3 ms·
Tailwind has some nice ideas, but boy oh boy is that ecosystem a mess of tool chaining. The barriers to entry are low (e.g. "just npm install [thing]" then init
by Someone1234 4y ago
Tailwind has some nice ideas, but boy oh boy is that ecosystem a mess of tool chaining. The barriers to entry are low (e.g. "just npm install [thing]" then init), but maintaining, updating, and dealing with conflicts between all these tools is an absolute nightmare and getting worse rapidly (and, no, the "Play CDN" version of Tailwinds doesn't mitigate anything because it isn't supported in production).
Bootstrap for all its critics, is just "reference the library, reference your theme, and you're done." You want to upgrade? You can just have individual pages referencing different versions at the same time, without npm reconfiguration.
- solumunus 4y agoBeen using Tailwind for years and it's smooth as anything, basically set and forget in every project for me. Would hate to work on projects without it at this point.
- interstice 4y ago> You want to upgrade? You can just have individual pages referencing different versions at the same time Not sure if I’ve just never seen it done well but this sounds like nightmare fuel
- PaulWaldman 4y agoWhat issues do you have with the Tailwind toolchain? I've had a dissimilar experience with Tailwind using the executable CLI. Just create a config file, tell it what directories to monitor and the output of the resulting CSS. >You want to upgrade? You can just have individual pages referencing different versions at the same time, without npm reconfiguration. You could use two different versions of the executable CLI and output two different versions of the resulting CSS when migrating portions of the application to a different version.