Very much enjoyed reading this post, Dakota Lee Martinez. I’ve only recently been introduced to Tachyons, and have the opportunity to start implementing it on a rebuild of my company’s web app.
My research on modern CSS has sort of blown my mind—in the same way that JS frameworks were (are?) kind of all over the place, CSS seems to be going through a similar revolution. In my biased opinion, the React model of UI components has kind of won out on how to build complex client-side projects.
react(state) → UI is as simple and declarative as it currently gets, and your opening paragraph seems to concur with this sentiment.
When we’re working on building functionality, we understand that the best way to do that is to have a bunch of functions or methods that just do one thing, do it well, and don’t rely on a knowledge of their context to do their job
I love this statement, and it’s a huge reason why Tachyons has sort of won me over. When I want to design something, I think about it in small increments.
I want to add some padding; then change the color; then add a border; then update the color; etc.
Being able to literally “tack” these thoughts onto a component as I think about them—and not worry that my changes are cascading all over the place—has been so much fun.
The real struggle now is convincing my teammates it’s the right choice ;)
PS — thanks for the tip on having a web page with the library’s source open while developing, this has been wildly helpful in terms of development flow as I learn the short-hand class names.