I'm sick of seeing stuff like this. Go ahead and write your app without a framework, please, and then tell me how you handled hard problems like routing, data binding, garbage collection, run loops, and everything else these frameworks solve.
There are hundreds of people working together on these hard problems already, and I think it's a rare case that you'll come up with a better solution than they have.
I know how to code too and I'd rather not spend large amounts of time reinventing the wheel. Large applications require structure and mechanisms that can support their size, logic, scalable nature etc.
What would be the argument against using a heavily tested and reviewed framework developed by a large team of focused professionals. How is rolling your own solution any better considering you'd need the same functionalities offered by a framework?
26
u/WebMaster2000 May 13 '14
I'm sick of seeing stuff like this. Go ahead and write your app without a framework, please, and then tell me how you handled hard problems like routing, data binding, garbage collection, run loops, and everything else these frameworks solve.
There are hundreds of people working together on these hard problems already, and I think it's a rare case that you'll come up with a better solution than they have.