That’s why today, I hope he won’t mind if I expand his thought to declare the revisited Atwood’s law (calling it Atwood-Giraudel would be quite presomptuous):
[A]ny application that can be written in Sass, will eventually be written in Sass.
And given my obsession for Sass, I’ll go even further and add this extra part to the quote, even if it won’t ever be retained:
… and chances are high that it will be done by me.
Nonsense you say!
Sass is 7 years old if no mistake, and has come a long since its early days. In 7 years, and especially because of silly people like me loving doing crazy shits, a lot of stuff has been made in Sass already. Let’s see:
- a JSON parser;
- bitwise operators;
- sorting algorithms;
- functional programming;
- Levenshtein distance implementation;
- inverse trigonometric functions by Ana Tudor…
And there are countless more examples I’m probably not even aware of.
How did we get there?
I think the main reason is it’s challenging. Because Sass is a very limited language, doing advanced things can turn out to be quite challenging. And as we all know, challenge is fun.
Aside from being fun to write, it actually helps a lot understanding the language. I would not be that skilled with Sass if I had stopped after declaring a couple of variables and functions. You don’t get good by doing what everybody does. You get good by pushing the limits.
I think I could not stress this enough: try things folks. Do silly stuff. The only rule is to remember what is an experiment and what belongs to production code. Don’t use experimental/crazy code in a live code base. It doesn’t smell good.
Any application that can be written in Sass, will eventually be written in Sass. And we are already close to the end.