4 ms·
This after one or two lines of text feels like an evolved rant by someone who had a specific issue with a specific framework and tries to justify their drastic
by AstralStorm 11y ago
This after one or two lines of text feels like an evolved rant by someone who had a specific issue with a specific framework and tries to justify their drastic steps or NIH.
All abstractions have warts and frameworks are no exception. An annoyance that is well known and cannot be easily fixed is no reason to throw out the baby with bathwater.
- esailija 11y agoFrameworks are all or nothing, that is how they are different. Or does it make sense to have a codebase that has a mix of angular, react, backbone and ember for instance? Of course not. They are nothing like libraries in this regard.
- AstralStorm 11y agoCorrect, which is why the choice of the framework should be done intelligently and not haphazardly. A good framework is flexible enough to handle weird corner cases with grace. Sadly, this is often lacking in the frameworks for web development. The author suggests not using any frameworks at all, while instead they probably should write what they or most everyone should look for in one.