Anonymous
asked:
what made you opt for tailwind css-in-html for cohost org?
so fun fact: i actually used atomic CSS professionally at a job back in 2013, on a pre-1.0 angular.js app. it was miserable because we didn't have good tooling, and when i first learned about tailwind i assumed it would be a similar situation.
turns out! tailwind has VERY good tooling! using it was largely my decision. for a very small team like ours, it acts as a massive force multiplier; we're able to make changes faster than we would otherwise and have a consistent set of rules for quickly implementing new designs.
i do not think tailwind would be good for a large team. if we keep growing staff, there will likely come a point where we need to move to a more traditional semantic CSS system. but i also don't think we could have launched cohost just using semantic CSS, or at least nowhere near as quickly as we did.
