I continue to be surprised that new platform-level CSS features seem to be rolling out so fast that framework and library abstractions on top of CSS are having a hard time keeping up.
Feels unprecedented but it’s a huge vote in favor of Writing CSS as CSS in CSS.
29 replies
“best practices don’t want to actually work any more”
-
-
@zachleat Wow. What an incredibly cursed sentence. 🫠
@chriskirknielsen my job here is done
@zachleat If you are bad engineer, best practices won't save you.
-
@zachleat npm install css-in-css
@zachleat Is this to be C-CSS-SS or CS-CSS-S?
@philsherry I think CCCSSSSSS is accurate
@zachleat CSS in any non-JSX framework is also just writing css as css*, so this also applies to them 😁👍
(* you get optional scoping to components)
@zachleat Makes me glad that decided to bail on using Sass.
@bobmonsour I still use Sass on my blog fwiw!
@bobmonsour @zachleat Also possible to write CSS in scss. Although these days I prefer plain CSS with Lightning CSS to even out the edges!
@zachleat css-in-css? Can’t see that catching on
@zachleat surely we should use CSS.AI. CSS writing CSS as CSS in CSS?
@zachleat 10000% agree. Facing battles with this in so many areas. Just recently, with tailwind breaking when using a cascade lager named “base”, without wanting to actually use tailwind the specific file. Nasty.
@zachleat browsers peaked with <blink><font color=red>the font tag</font></blink>.
@secretgeek I… have concerns
@zachleat concerns that you are free to put in a <marquee> tag and i'll be sure to read them as they scroll past.</marquee> (Best wishes)