4 ms·
I thought tailwind was a terrible idea when I first looked at it. Many months later, I tried it on a side project, and really didn't get it at first, thought af
by corytheboyd 6y ago
I thought tailwind was a terrible idea when I first looked at it. Many months later, I tried it on a side project, and really didn't get it at first, thought after ~2 full days of working with it I felt very productive. The people who dismiss things without trying them will continue too I suppose, I just hope I don't end up having to work with them in a professional setting :P
- benatkin 6y agoIt's better to reject a 3MB boilerplate CSS file out of hand. Some things are better left untried.
- weaksauce 6y agoexcept that shows that you haven't used tailwind at all if you think it's a 3MB CSS file... it's literally a postprocessor that strips out all the unneeded styles from the palate before you ship it. much, much smaller than 3MB. https://tailwindcss.com/docs/optimizing-for-production https://tailwindcss.com/docs/optimizing-for-production
- benatkin 6y agoI said I hadn't used it, so that is true. I have looked into it only briefly, but I understand the 3MB CSS file just fine. Yes, it's only in development, but it's still something I'd rather do without.
- papertokyo 6y agoDev mode on any kind of frontend framework sacrifices bundle size for developer productivity. I've never worked on a Tailwind project that ended up with a CSS file larger than 11kb in production for a whole website, and that's what ultimately matters.
- corytheboyd 6y agoWhy do you have to double down on this stance if you admit to having never seriously used it? Debug builds in any low level compiled language are also larger, because they include useful debugging runtimes, are you also against that? Sorry if I did not use the exactly right words to explain this, or if I too am just wrong about whatever you're talking about. Where does this anti-frontend-engineering madness end?
- benatkin 6y agoHow on earth is that an admission? I said I decided not to use it right up front. > Where does this anti-frontend-engineering madness end I love frontend engineering and I would work on a tailwind-based project if I had a strong need or desire to work on it for other reasons. If I was picking between two projects and all other things were equal, I'd choose the non-tailwind one, though.
- corytheboyd 6y agoSorry, I was a bit rude to you in my first message, and projected my being upset about a lot of other anti-frontend sentiment I was into to be honest! I think we’re on the same page about generally picking what’s right for a project, even if some of our individual choices don’t line up— and that’s totally fine! We’re lucky to have so many free tools tailored to so many specific needs, and it’s okay when some of them are very similar, they can still both be valid!