3 ms·
Sure, but still, it's the kind of small-but-incremental QoL improvements that apparently frontend designers really really want in their working week. You linke
by piaste 4y ago
Sure, but still, it's the kind of small-but-incremental QoL improvements that apparently frontend designers really really want in their working week.
You linked to a very interesting TS library above, vanilla-extract, and you can probably see that what it does is very similar to what Tailwind does, only plugging into 'tsc' instead of PostCSS? Eg. https://vanilla-extract.style/documentation/styling/#media-queries https://vanilla-extract.style/documentation/styling/#media-q...
- satvikpendem 4y agoIt's just using camelCased CSS similar to Emotion or styled-components, how is that similar to Tailwind at all, it's not atomic? Unless you simply mean that both Tailwind and VE have a build step, which is, well, vacuously similar. VE also runs PostCSS underneath after it compiles to CSS, so you can use whatever plug-ins you want too. Regarding the QoL, it seems more to me that now Tailwind discovered that they have to support arbitrary CSS as well as every new feature, so they have to manipulate their DSL to fit all of that into their current syntax, ie class names, even if it doesn't fully fit. I'd rather just use CSS at that point, if I'm cramming a bunch of stuff into a class name.