At the risk of being labelled a one note pessimist, pretty much everything about the state of CSS—slow uptake of standards, popular reliance on frameworks, the lack of conferences, and the diminishing number of publications—can be explained by the eradication of CSS specialisation from the job market
Edited 90d ago
@baldur I also see the "self-eradication" of some developers (outside the mainstream), trying LLMs instead of learning, thus producing even more outdated (& unmaintainable) CSS.
I actually wished we had slower feature rollouts on the web (slower-but-simultaneous across engines). But I also wished we could do something about the long tail of engine updates.
On a related note: I just removed an instance of @supports (display: flex) from a code base at work 😉
@pkra Yeah, people relying on chatbots for learning and not realising that what they get is both inaccurate and outdated (with training data having an inevitable cut-off date) is something I keep seeing more and more 😕