Sort of but it just builds on top of cruft. CSS and html is poorly designed to do what we are doing with it today.
Like I understand the point of not building bloat. But the reason why people build bloated stuff like react is because the primitives are just raw shit. HTML and css is just really bad.
Oh? All things considered, I believe html and css are both great. Incredibly flexible and very easy to get a basic "framework" started for consistent design
Everything else I've used to date (for UIs) was either extremely limited or way more complicated to use in comparison
I personally feel like the only thing we're missing is a way more aggressive deprecation policy. Not actually removing the API, just clearly signal that you would probably be better off not using it in 2025.
CSS is incredible technology, but holy shit does it feel archaic in a large Typescript project to have a massive design system in a string.
Why can’t I click an element and see the css files that apply to it? Why can I get autocomplete for my utility classes and custom properties? I would happily nuke CSS from a project for a typescript library that could marry the two worlds with minimal trade-offs, but I’ve yet to have the time or courage to dive into a library like vanilla-extract: https://vanilla-extract.style
Like I understand the point of not building bloat. But the reason why people build bloated stuff like react is because the primitives are just raw shit. HTML and css is just really bad.