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.
@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 always confused me the appeal of frameworks, when you could just become really fluent in CSS, especially with all the dynamic stuff you can do these days
Add comment