A great an opinion, which I once held. But when I looked deeply I only saw benefits.
I see tailwind as a damn cheat (a good thing), a hyper productivity tool throwing away all the what we learned as 'correct', and just get things done with escape hatches to fallback.
- Rapid prototyping with tailwiwnd
- Making component frameworks like bootstap? Just use tailwind sass with helpers. You can use a sass approach with including the helpers so you dont polute your DOM.
- it is easy to remember and guess which increases velocity. p-1/2 etc.. m-1 p-2 etc etc. Conventions make sense!
- Bloat can be solved with purge
- Refactoring easy easy if you abstract it away in sass so you can make global style changes.
- Protyping is easy, and you can then move it towards a component framework once you've done wiggling around and changing your stuff.
- I find css in components hard and painful personally also makes doing broad style refactors a bit more difficult.
- I also use css for email and other simple landing pages that dont require html components or react/webcomponents or whatever.
I find this a great addition to my life. Its a darn sharp knife, up to you what you do with it.
Bloat can be _partially_ solved with purge. You still end up with a somewhat larger HTML file because of all the extra class names you have to write. To me Tailwind is worth the extra bytes, which, after all, probably doesn't represent that much of an increase in file size.
For sure but and even if you find that too much you can just use the helpers in SASS and you can just write your plain old classes and then tailwind is just another sass framework.
I see tailwind as a damn cheat (a good thing), a hyper productivity tool throwing away all the what we learned as 'correct', and just get things done with escape hatches to fallback.
- Rapid prototyping with tailwiwnd
- Making component frameworks like bootstap? Just use tailwind sass with helpers. You can use a sass approach with including the helpers so you dont polute your DOM.
- it is easy to remember and guess which increases velocity. p-1/2 etc.. m-1 p-2 etc etc. Conventions make sense!
- Bloat can be solved with purge
- Refactoring easy easy if you abstract it away in sass so you can make global style changes.
- Protyping is easy, and you can then move it towards a component framework once you've done wiggling around and changing your stuff.
- I find css in components hard and painful personally also makes doing broad style refactors a bit more difficult.
- I also use css for email and other simple landing pages that dont require html components or react/webcomponents or whatever.
I find this a great addition to my life. Its a darn sharp knife, up to you what you do with it.