published by Holger Bartel on :: reading time: ~1 minute
When we started to work on Colloq, we agreed to write good, old, plain CSS. I was a little sceptical at first and thought we’re not going to like it much.
After a few weeks I had totally gotten used to it and started to write “Vanilla” CSS for all my other projects as well.
It has now been over a year that I haven’t really used Sass anymore and sometimes find myself wondering why on earth someone would want to still use it. I don’t miss it a bit.
Granted, one helpful feature are variables and especially so for colors. For me this rather small advantage isn’t enough reason to go back to using Sass though.
One of the best outcomes of moving back to writing plain CSS is that you learn to properly write (and understand) CSS again. Just like in the old days, where you have control over every single line of CSS you write. Or don’t write. As a nice side effect, you end up with a pretty small codebase, which benefits performance, amongst other things. For example: On Colloq, which has now grown into a fairly large application, we deliver only 35Kb of compressed CSS for the whole site.
By being open to try something “new” again, a decision that I thought to be a bad idea turned out to not only benefit in various areas of development, but also brought back a lot of the joy of writing nice, clean and scalable CSS.