4 ms·
i know tailwind wasn't created in a vacuum and solves a massive problem. but part of me does feel sad it "won" and now we all are forced to deal with it in one
by sergiotapia 2y ago
i know tailwind wasn't created in a vacuum and solves a massive problem. but part of me does feel sad it "won" and now we all are forced to deal with it in one way or another. i remember when HTML was clean and semantic, and crawlable. there was a certain respect in that way.
- _heimdall 2y agoIt won mainly because it was a much better solution for styling in react than what existed at the time. In react today I'd still probably reach for Tailwind. In any other scenario I'd only reach for it I wasn't comfortable with CSS.
- earthboundkid 2y agoYou can’t remember a time that never existed.
- hecanjog 2y agobootstrap won just a few years ago. something else will win soon. edit: I'm trying to impress the fact that things change. looking at if this library "won" or not misses the point.
- dartos 2y agoI think 10 years is a good metric for “won” in FE land. React “won” Wordpress “won” Java applets did not Those iPhone web apps that were around before the App Store should’ve, but didn’t. Tailwind undecided
- ducktective 2y agoVue did not win, right? Seems like nowadays Svelete took its place, though still undecided imo
- dartos 2y agoBoth are still around, but in the space of frontend frameworks, React is currently the winner.
- naasking 2y ago> i remember when HTML was clean and semantic, and crawlable I'm confused, HTML under tailwind is not any less semantic than under any other CSS toolkit.