Lovable was a TailwindCSS recombinator, that’s it.
Lately it is more and more ShadCN as well.
TailwindCSS is a masterpiece but ironically doesn’t really get its fare share while “Build on top of TW” frameworks make money.
TailwindCSS is the final evolution after all other frameworks always had its benefits but also massive limitations.
BEM anyone?
TW is really elegant a new paradigm in its purest sense and brilliantly executed. No wholes could be poked in it for years and the extensibility shows, how brilliant it is.
Bootstrap will always be held dearly but it was about browser quirks etc first. Important milestone but stands no chance against TW.
personally I went back to bootstrap when LLM vibecoding took over. 10yo old patterns and even weak model can oneshot anything blindly, at scale. react+bootstrap is kind of cheat mode for frontend dev now with zero confusions about specific classes or api version changes of selectors and what have you, this is stupid solid after all this time.
As a dev manually typing I loved tailwind for sure, with LLMs not so much, and bootstrap in particular nails it the best IME. and yeah one can customize bootstrap quickly to look however it should, just tell your frontier LLM of choice your wishes.
Am I the only one who doesn't like Tailwind? The way it totally pollutes your html makes it seem like, while the benefits are impressive, they're not worth the collateral damage.
You are not the only one. I also dislike it immensely. For a framework that established itself as "for developers who don't know or want to learn CSS", polluting the HTML in the manner you describe makes no sense. And no company I've worked at figured out how to prevent it from becoming a bloated, impossible-to-maintain mess.
Tailwind is fantastic precisely because the biggest benefit (tree-shaking to minimize the CSS that ships) massively outweighs the fact that Tailwind syntax "looks like" an anti-pattern and makes your code "look" ugly. Also, you get used to bundling your styling and JS code in one place with any component-driven framework like Next.js/React, and Tailwind works seamlessly with all of them. I guess I just prefer the benefits to the alternative, and I feel like the collateral damage of the alternative is definitely not worth trying to make front-end design code look simpler.
I'm in the same boat. Tailwind always seemed insane to me, even after really giving it the benefit of the doubt and trying it out. I use it now only because its so easy for the LLMs to use, so I don't need to actually interface with it at all.
The idea of style being separate from content is great for something like a blog or a wiki article but when you're building an app each design needs completely different html and then it makes sense to couple. No naming. No hunting down styles. The html is your ccs. You get a formatter to sort the classes and it will compress away all the repetitive junk. Besides who looks at code much these days anyway.
It's pretty much all personal preference. You can do anything with css modules, or use any other CSS extension.
I don't ever recall hearing about the specific, tangible benefits tailwind brings. Just a loose "it's faster", or "it's easier". It just feels like one of those things, in front end development, that are just hype-driven rather than actually bringing any ostensible benefit.
Lately it is more and more ShadCN as well.
TailwindCSS is a masterpiece but ironically doesn’t really get its fare share while “Build on top of TW” frameworks make money.
TailwindCSS is the final evolution after all other frameworks always had its benefits but also massive limitations.
BEM anyone?
TW is really elegant a new paradigm in its purest sense and brilliantly executed. No wholes could be poked in it for years and the extensibility shows, how brilliant it is.
Bootstrap will always be held dearly but it was about browser quirks etc first. Important milestone but stands no chance against TW.