Blog
Mert Özen's blog posts on software development, backend, frontend, and DevOps.
Is Sass Still Needed in 2026? Comparison with Native CSS and Setting Up Dart Sass
Yes, but not everywhere it used to be: variables, nesting and color/math are native CSS now, while mixins, loop-generated rules, maps, the module system and compile-time errors are still Sass-only. We measure why raw SCSS leaves not a single rule in the browser, compare sass with sass-embedded, and add Sass to Angular, Vite and ASP.NET Core.
Preparing for Dart Sass 2.0: Deprecations, --fatal-deprecation, Slash Division and the End of @import
In Dart Sass 2.0 most deprecations added up to 1.105.0 become errors (slash-div, color functions like darken(), the legacy JS API), while @import, global built-ins and the old if() stay warnings until 3.0. We get those errors today with --fatal-deprecation=dart-sass-2, clean up with sass-migrator, and show that Angular's hard-coded quietDeps hides deprecations in files loaded through includePaths from the build entirely.