3 ms·
I'm also not a fan, but for bootstrap you have to understand how those semantic class names turn into CSS and presentation, whereas the bottom is directly telli
by zumu 4y ago
I'm also not a fan, but for bootstrap you have to understand how those semantic class names turn into CSS and presentation, whereas the bottom is directly telling you what it does. It also gives you a lot more flexibility out of the box.
Tailwind accepts greatly reduced DRY for straightforwardness. It's kind of like inline styles with training wheels.
I'd much rather do this type of thing in the CSS layer, but doing it inline has advantages. Mainly, I think the reason it's caught on is new junior devs get productive in it very quickly.
- bredren 4y agoBootstrap templates contain examples and simple utility classes though. They prepackage bundled JS for interactivity, skipping over any build process. There are also way more websites running bootstrap that need maintenance or enhancements. These seem like a better fit for junior programmers. I think tailwind has caught jr programmers because course sellers have had an easier time getting market share because there isn’t remotely as much (free) content, examples and docs about tailwind. I think the influence of people with a vested interest in selling courses (like the hosts of Syntax web dev podcast) is what gets people to choose newer frameworks, not practicality or employability.
- JUNGLEISMASSIVE 4y ago[dead]