5 ms·
This ignores the problem of not using a framework, that is, for a sufficiently complex project you will eventually end up with your own ad-hoc framework if you
by windlep 11y ago
This ignores the problem of not using a framework, that is, for a sufficiently complex project you will eventually end up with your own ad-hoc framework if you don't use an existing one. Maybe it's better, maybe worse, but one will appear regardless.
That's how Django and Rails started (and I'm sure many more). Ad-hoc frameworks that then get yanked out of the project so the company can re-use the useful parts.
I've seen quite a few ad-hoc frameworks companies have inadvertently created in their effort to "not use a framework", rarely were they nearly as good as what was already out there in the OSS world.
- wwweston 11y ago> you will eventually end up with your own ad-hoc framework Or some people call it, "code that solves the problems we actually had."
- raverbashing 11y agoWhile creating 10 other problems usually Sometimes I agree that using a home-grown solution is better, but you don't want to reinvent what took a lot of time and a lot of people to work through (like Frameworks, DBs, etc)
- ng12 11y agoThat is virtually unmaintainable. What happens when Joe Hacker moves on to greener pastures? The new guy gets stuck with a framework that he can't Google. This is where the author lost me: > You've to ask for expert help, wait until someone helps you or pay an expert framework consultant. The ability to ask an expert for help is a boon, not a curse.