5 ms·
I agree that fragmentation is a problem, but don't understand why the solution to that problem should be smaller, fragmented libraries instead of larger, comple
by rurabe 12y ago
I agree that fragmentation is a problem, but don't understand why the solution to that problem should be smaller, fragmented libraries instead of larger, complete frameworks. Isn't that the same problem described in combining all the tools with small market/mind share? In my experience, far more problems arise from the interaction of separately authored modules versus the interaction of modules designed to work together. Not to mention that there will be far more blogs and SO posts about a larger framework.
- bsaul 12y agoI came to say the same. If you multiply the number of dependencies, owned by different people, having different interest, you multiply the chances of having to catch up with a problematic update. On a more general pov, the debate between "integrated design" and "modularized" design has been going on for decades. We know the advantage of both. The problem right now is that angular made a desition to break compatibility in a major way while their framework was barely becoming mainstream. Let's not make it a bigger problem. People that invested in the .net framework, or in the unity framework, did not make a blunder. All we need is an equivalent in the front end js world.