4 ms·
This is a low quality flamebait article. > Very rarely is the added complexity of frameworks justified and the added risk of breaking stuff down the line makes
by Tainnor 5y ago
This is a low quality flamebait article.
> Very rarely is the added complexity of frameworks justified and the added risk of breaking stuff down the line makes it a NO GO for serious software deployments. Only toy software and very small applications can justify the usage of frameworks and the likes.
There are definitely downsides to using frameworks, but this statement directly flies in the face of evidence. There's a ton of commercially successful software using frameworks, just think of all the things that are powered by React, Ruby on Rails or Spring Boot.
- thomascgalvin 5y agoI find the idea that I, sitting in my basement office, could hand-craft something nearly as powerful and maintainable as Spring Boot, as part of the project I'm actually working on, totally laughable. And the idea that this bespoke framework would somehow be more maintainable in five years is just lunacy. Even if Spring falls out of fashion, you'll still be able to find people that have a decent knowledge of Spring in five or ten years, just like you could find people who knew COBOL in the 90s. But how are you supposed to hire for "some guy that can figure out WTF this dude was doing when he wrote his own ORM a decade ago?"
- postalrat 5y agoHow many frameworks can you fit into one app?