The article discusses the evolution of CSS and the emergence of pre-processors like Sass and post-processors like PostCSS. Pre-processors allow developers to write SCSS or LESS, compiling them to valid CSS. However, post-processors are gaining an upper hand with tools like Autoprefixer, which simplifies vendor prefix usage. Key factors contributing to this shift include native CSS's advancement with essential features like variables and nesting, as well as the emergence of new post-processors such as Lightning CSS that streamline development further.
CSS pre-processors existed in the first place because native CSS lacked features that were critical for most developers, including CSS variables, nesting, and conditionals.
Post-processors have always been on the verge of winning since PostCSS has always been a necessary tool in the toolchain, especially with plugins like Autoprefixer.
Native CSS gaining essential features has shifted the balance towards post-processors, as developers no longer have to rely heavily on pre-processors.
Lightning CSS has emerged as a noteworthy post-processor, signaling a new wave of possibilities for streamlining CSS syntax and processes.
Collection
[
|
...
]