There's a lot of hype going around in Web Development. Every now and then a new framework/library/tool appears that gets the attention of many de...
For further actions, you may consider blocking this person and/or reporting abuse
TailwindCSS solves a lot of problems for a lot of developers. That's great! But I'm not so keen on using it because I prefer to just use custom CSS. But if I needed to reach for a library I'd probably go with Tailwind.
I get why it's helpful for many people. I really appreciate that. Personally, I'd prefer to know CSS deeply and just use my own styles. That way I can use raw css, scss, styled-components, etc.
I like how you went custom and made your own tool! To me, that's more interesting because there's the opportunity to allow customization of CSS before it reaches the .css file. Facebook has an interesting custom solution that compiles down to raw CSS but removes any clashing styles and dead css.
I am sorry that you are finding TWCSS a bit difficult to integrate with directives. But why would I want to use CSS in JS in the first place? TWCSS is a CSS in the first place, looking at your review one might think you feel the same for the SASS as well...TWCSS miht have its downsides for sure but it is certainly not a directive creation. I have been working with TWCSS for a long time now and did not find any major flaw, and to sum up it seems you haven't been using it very thouroughly to give a honest review. I mean even in the official tutorials creator suggests to create own directives so that the code is more readable, and to use it directly in the html for quick tweaks. And e.g. even if you have a long string of css classes in the html, once you are done with cssing you can extract it without any pain. I am not a TWCSS advocate, even if I have written 2 articles about TWCSS, but I did not read here any concrete downside.
This is not so much a review as it is a hijacking of TWCSS to shamelessly promote his own framework. 🤦♂️
I don't see that at all. The author pointed out the good and bad things about TailwindCSS and had a custom solution. Nothing wrong with that! I love seeing people's creativity.
That's what the cascade is for! The big C in CSS that everyone seems to be trying to get away from these days. You have something like an aside that is styled as a sidebar, and you give it colours and so on, and elements within it inherit those.
Tailwind is another big push towards binding content and style.
Yes, I've seen people talk about "tooling" with Tailwind. As far as I can see it's an acceptable way of using it - in fact, it's the only acceptable way of using Tailwind as far as I'm concerned. Anything that wants me to add
text-white margin-smallto a redundantdivis completely off the table.So, tooling fixes that? It does... but it's a lot of work to get back to the original problem. Tooling in Tailwind is reinventing the wheel.
This concept is excellent. One step closer to turning Css Into a real language instead of a DSL with no real tooling. How does it rate with refactoring ability and finding duplicates?