4 ms·
A lot of people like the larger, more thorough frameworks because: 1. they think it makes newer devs can feel safer 2. dev teams can simply agree on an pre-ma
by TiredGuy 5y ago
A lot of people like the larger, more thorough frameworks because:
1. they think it makes newer devs can feel safer
2. dev teams can simply agree on an pre-made modus-operandi for all css without having to have discussions/evolutions on it.
But for 1, it also gives newer devs a steeper learning curve, and it gives older devs Yet Another Framework to learn and then possibly discard in a few years. It's also often used like a crutch, where yes the newer dev may feel safer, but they're also not exposed to as many discussions or reasoning around well-organized styling, cleaner semantics, etc.
And for 2, it can also add overhead to dependency audits and often for the large frameworks with pre-made components you can end up spending significant resources fighting/working around the framework components when the inevitable unforeseen use-cases come up
- glacials 5y agoI see a bit of straw man here -- thorough frameworks are often liked _because_ they're thorough. Simple.css looks fantastic and I'll reach for it next time I make a simple personal site, but for a professional website with a hundred pages and design considerations that go way beyond "it should look pleasing", I need more levers, leverage, and turnkey components.
- TiredGuy 5y agoI certainly see your point that any unsatisfactorily complete benefit-drawback list is going to seem like a strawman. I meant to point out some of the more commonly stated benefits and contrast them to the less commonly considered drawbacks, but I would also enjoy seeing this thread evolving into a more complete list. I also agree with your other point that that is a benefit for having more bells and whistles in a single branch of dependencies.