4 ms·
Bah. Why monolithic frameworks suck. If the framework is implemented as a bunch of nicely integrated yet modular libraries that you can use standalone, you can
by Hexstream 17y ago
Bah. Why monolithic frameworks suck. If the framework is implemented as a bunch of nicely integrated yet modular libraries that you can use standalone, you can use the fork without the knife and plate.
- natrius 17y agoPart of the benefit of monolithic frameworks is the third party tools built on top of it. If you choose libraries independently, you've avoided reinventing a few wheels, but there is more functionality you could avoid reimplementing than just the basic database interaction, template system and request handling.
- Hexstream 17y agoThere's a bit of a paradox here: a monolithic framework gives you less choice because you can't use only a part of it without great pain, however you have ostensibly more choice of functionality from third-parties since there's a standard way to use it that's hard to diverge from. But if you're any NIH on the side, the framework-as-bunch-of-easily-integrated-libraries approach really makes more sense. It also lets you try a framework incrementally, therefore decreasing risk instead of committing to a behemoth framework prematurely.