The article addresses the challenges CSS developers face due to inconsistent browser support for modern features. The author emphasizes the importance of feature detection, progressive enhancement, and the use of tools like CSS pre-processors (Sass, Less) and post-processors (PostCSS) in the build pipeline. These tools simplify organization and enhance functionality, bridging the gaps until native CSS evolves to include essential features. The evolution of CSS reduces reliance on pre-processors, while build tools enhance efficiency in compiling and optimizing code.
Even if browser vendors all have a certain feature released, users might not have the latest versions! We can certainly plan for this a number of ways.
Pre-processors do not just provide organizational superpowers, though. Sass gave us a crazy list of features to work with, including: ... such as mixins, functions, and nesting.
CSS has evolved a lot since the release of Sass - we have so many of those features in CSS today - so it doesn't quite feel that way anymore.
PostCSS is the big one here, giving you tons of ways to manipulate and optimize your code, another step in the build pipeline.
Collection
[
|
...
]