Haven't written frontend in a few years but honestly for me CSS Modules solved the scoping issue and all the CSS in JS/Tailwind stuff since then feels like a red herring.
RedShift1 · 32m ago
Maybe CSS in JS was the wrong thing to begin with. Your developers were so preoccupied with whether they could, they didn't stop to think if they should.
breakingcups · 5m ago
I was about to say the same. Having lived mostly in Vue land, this quote felt astounding to me:
"The React team themselves have made it clear: runtime CSS injection will always be slower than statically extracted styles. They recommend using <link rel="stylesheet"> for static styles and inline styles for dynamic values. That's the future."
I thought this lesson was already widely learned since the jQuery days.
jeswin · 17m ago
It might seem like a terrible idea now. But when it was first introduced, a) people were still trying to get CSS and Components to work together, React having made components quite popular; and (b) React was actually usable, compared to the complete mess it's become now, especially after they introduced hooks.
I switched to web components for all my personal work.
mootoday · 26m ago
I came to post the same comment :-)!
reify · 26m ago
Does this mean I can eat 40% faster when I use a fork.
if so, I shall set the dining table without knives.
there is no spoon!
dalf · 23m ago
You might not have a fork if you dine with philosophers
"The React team themselves have made it clear: runtime CSS injection will always be slower than statically extracted styles. They recommend using <link rel="stylesheet"> for static styles and inline styles for dynamic values. That's the future."
I thought this lesson was already widely learned since the jQuery days.
I switched to web components for all my personal work.
if so, I shall set the dining table without knives.
there is no spoon!
( https://en.wikipedia.org/wiki/Dining_philosophers_problem )