Before you complain about CSS problems at scale or request new features, you should read the design principles behind it
Currently CSS versioning is a mess with countless separate modules, CSS3 literally refers to anything beyond CSS2.1, and there is no such thing as CSS4
Being able to process and transform CSS before running in browser is powerful and open to a lot of possibilities
Starting out with mostly latest cutting-edge CSS features then adding fallbacks gracefully
Starting out with mostly basic widely-supported CSS features, then adding newer ones if supported progressively
Error handling in CSS is taken care by CSS parsers where bad or unsupported syntax will be stripped off and recovered gracefully
Assess your CSS proficiency today after years of styling websites, you might be shocked at how much you don't know
Whether you should start using utility-first CSS in general or Tailwind in more specific?
Modern CSS has moved away from manual vendor prefixing in favor of automatic prefixing and feature queries
How CSS optimizers work under the hood by applying different minification techniques on CSS files resulting in smaller file size