loading...

re: Why You Shouldn't Use A Web Framework VIEW POST

TOP OF THREAD FULL DISCUSSION
re: but if you work with a team, you need a standard structure for people to working together. for me, that is the point of having a framework. Have ...
 

It isn't necessary, it just costs time to roll-you-own. Which means money (salary mostly) and opportunity (time-to-market mostly).

When you use an existing framework you save time in at least these areas:

  • Writing documentation and keeping it up to date
  • Getting a new hire up-to-speed
  • Implementing new features
  • Guarding against security vulnerabilities^
  • Getting answers to questions without costing the time of a teammate

^ Security is a big one, Rails for example has a bounty program for finding and reporting vulnerabilities. Is your team paying someone to find security vulnerabilities so you can patch them before they are exploited?

code of conduct - report abuse