Post

and yes!

Yes

It is impossible to have `-in-JS` in the ecosystem name and not create the impression of affecting runtime. And yet there are so many examples that are also `-in-JS` but leave almost no footprint on the browser's runtime or the bundle size

CSS-in-JS and styled-components are spelled differently enough to be considered distinct terms. Beyond the two I mentioned, there are even more libraries that are even more distinct and have histories dating back to the time CSS-in-JS was coined

Yeah, it smacks of that kind of navel-gazing over-engineering, where someone is probably proud how their proprietary design system improves on vanilla CSS by adding terse cascading styles that can be easily applied, once learnt. And then someone added !important to a component and messed it all up 🤷

I’m not a fan of CSS Modules anymore either, but the crucial difference is that there’s no more runtime. The object only contains a map of class names.

It's classic Cassandra complex.

the cascade was never the problem, it was just the first thing we could blame without reading the spec

CSS in JS has always CONFOUNDED me as a designer.

And at least LLMs weren’t trained on that decade of inefficient tooling, thus ensuring this insane broken pattern doesn’t continue - oh

The blog post reads as if the result was some kind of a breakthrough. I wonder why they didn’t make it clear that they had an outdated stack, there’s no shame in that.

So painful 😖🫠.

Linaria et al emits plain CSS files 🤷‍♂️🙂

Lol in my React Performance course I explicitly advise not to use CSS-in-JS. 😂 Speaking from experience!