5 ms·
I'd definetly go for the framework approach. After building apps with and without frameworks, its a lot less painful to build upon something which exists alread
by tomdeal 16y ago
I'd definetly go for the framework approach. After building apps with and without frameworks, its a lot less painful to build upon something which exists already.
There are so many advantages to go framework, I can't tell everyone:
- frameworks are (mostly) under development, so you can benefit from trends and improvements in web development
- frameworks are well tested
- frameworks are more secure. Do you have all holes for XSS etc. closed? Are you sure?
- frameworks have almost always a community behind it, so you benefit from other users knowledge and plugins
- frameworks have plugins. You don't have to write anything from scratch, like DB connections, authorization or file uploads
- frameworks have documentation. Unless you are the sole developer of your app, you really want to have good docs.
Do frameworks have disadvantages? Sure, but I don't think it outweighs the advantages.
- theoreticalee 16y agoAgreed, a framework is just a toolkit of best practices and useful tools. Another benefit of using a framework is it lets you 'work' with other amazing coders. I have increased my php knowledge many times over by using symfony. Sometimes this happens because you just have to dive into the frameworks sourcecode to see what's going on.
- theoreticalee 16y agoIt's like having your own personal secretary do all the work and research for you to get the ground work up.. heh I like that analogy
- tomdeal 16y agoindeed! gotta save this quote somewhere :)
- eccp 16y agoAlso, if you need help at some stage, it's much easier to find someone with some knowledge on a framework (say, Symphony, since he built in PHP) than having to train that person into your framework and then the thoughts behind your application/idea.