4 ms·
let's not forget the HN mob is mostly back-end devs who will cheer for anything that gives them a quick and dirty way to style websites. These people have never
by nsonha 4y ago
let's not forget the HN mob is mostly back-end devs who will cheer for anything that gives them a quick and dirty way to style websites. These people have never needed to maintain a front-end codebase nor think about design systemically.
- agloeregrets 4y agoMillions of paid-only users here on a tight to the styleguide platform we built on tailwind with a team of FE devs with > 10 years experience each: Works great, HTML is easy to read instead of cross referencing classes, bundle output size is dramatically smaller. I'm not saying it is all sunshine and unicorns, just there are different perspectives, gains, and losses.
- lewisflude 4y agoSenior front-end engineer here! I hated, HATED Tailwind for ages. It made me super angry that it was glossing over everything that makes CSS great. The ability to write great, maintainable styles seemed lost. But after a couple of projects using Tailwind, I actually think it's a really solid way to implement styling that scales well as a project/team grows. It's maintainable because it's tightly coupled to markup (like styled APIs), has great first class support for design tokens and once you learn the syntax it can let you express specific css rules in a way that's more clear and concise. I don't know if it'll have much staying power as the front end community continues to explore how we want to define styles. But what is clear from Tailwind's success is people want high levels of performance, styles tightly coupled to markup, a first-class way to utilise theme tokens etc. For now if I was to start a new project, I'd likely pick Tailwind unless there was a good reason not to.