Hello, Code maked in CakePHP is good,bad or this not affect on nothing ? I ask because i pay some coder for make script and he make script in CakePHP, Now need some expert think about this CakePHP this not affect on nothing or ? Thanks,
It's a bad idea. It's better to code in pure PHP. So the next developer you hire needs to know CakePHP. Or if a framework becomes defunct you need to port it. Yes, frameworks can help speed up development, but it's lazy coding. There is the trust issue - do you trust that the code is (and always will be) secure?
yes, pure php is always better, frameworks always have one issues or another, also, you can't even make a tiny change on the site without hiring someone who can do it in that framework. plus there is always a sourcecode issue, *some* coders usually give the result code, and keep the source code to themselves, so you become locked to them only.
I think usually more professional developers would go towards using a framework of some sorts for any project. You shouldn't have an issue with anyone with PHP experience to work/modify existing code on any framework. A framework is just a collection of classes to make things easier for developers to develop. What is this script created composed of? Now, if this is a one class type of code, there is no use for framework. However, if it is an entire site it would be better to use a framework, even for you as a non developer to be able to modify things on the site as most frameworks are structured in a way to enable fast modification.
Hello, thanks for answer, On end framework don't have some bad side ? this on end give same results like clear php ? Thanks,
I use cakePHP on some projects and without knowing your business requirements it's impossible to say if it was the right tool for the job. Its not a bad tool, just not necessarily the right one. If your coder started from scratch and you wanted to hand the system over you would still have issues with getting the new person up to speed so don't worry about that. All the big frameworks are well documented and easy to learn if you are an experienced coder.
Actually using a Framework is wise. It forces a specific structure in coding and enables you to hire future programmers to expand the project. If your programmer didn't use a framework the next guy you hired would have to TRY to figure out the inner workings of the original programmers mind. If you've ever taken over someone elses code you know exactly how tedious of a process this can be. The fact that your programmer used CakePHP is a plus. Especially if you plan to have someone else make changes.
Using a framework is wise, IF you're able to keep within the framework for all your needs. Which isn't as easy as it might sound always. Proprietary code is, of course, also riddled with potential problems, but if it's well documented, and explains (either in comments, or in separate documentation) what to use where, and how to use all the functions and classes provided, it's hardly much more complex than learning a new framework. Of course, as long as a fairly well known framework is being used, you can usually find someone well versed in it already, and save on the educational bit.