If you are new to PHP, I suggest that you write some apps in PHP first and not try to use a framework. The problem with starting with a framework is that if something goes wrong you will have no idea on what went wrong, if you did somethign incorrectly or if the framework did something incorrectly. If you have only PHP that you wrote, you will noit have this issue.
Once you are comfortable writing PHP apps, then you can start to look at frameworks.
Sneha Heda
Greenhorn
Joined: Aug 08, 2012
Posts: 2
posted
0
Thanks Nick for quick reply. I have created an application using PHP, not many though But yes, for frameworks i am newbie. I was not sure which framework should i pickup to start. So, thought of taking views from forum. Hope you got my point.
New to PHP = don't use anything other than basic PHP. You will develop terrible programming habits if you start using external classes and applications. Those are basically for advanced developers who have become lazy, but still understand PHP's fundamental nature. Too many people are switching to things like Ruby on Rails (language) or depending on classes like jQuery (javascript) and Cake (php). Please, please, please try to learn the basics first. It's going to hurt a whole web of programmers down the road
Jared Drake wrote:New to PHP = don't use anything other than basic PHP. You will develop terrible programming habits if you start using external classes and applications. Those are basically for advanced developers who have become lazy, but still understand PHP's fundamental nature. Too many people are switching to things like Ruby on Rails (language) or depending on classes like jQuery (javascript) and Cake (php). Please, please, please try to learn the basics first. It's going to hurt a whole web of programmers down the road
It's always good advice to learn the basics of your chosen language. But once you've done that, there can be a risk of wasting a lot of effort (or money) re-inventing a square wheel instead of using the nice round one that's provided by a suitably well-written framework. Also, once somebody is paying you to build a serious application, you need to be sure you are developing robust, maintainable code as effectively as possible using standard approaches/components, and a good framework can help you to achieve this in a way that saves time and means the next person to pick up your code has a chance of understanding it because they know the framework.
FWIW, I used Zend Framework a couple of years ago and I found it to be pretty good. You can use it to create a full-stack application, or you can mix and match individual components, so you're not tied into a monolithic framework (like Spring or Rails), and ZF provides a huge range of components to support all kinds of functionality. From what I could tell, the code seemed to be decent quality, unlike many smaller PHP libraries out there!
ex-Oracle bloke
I agree. Here's the link: http://ej-technologies/jprofiler - if it wasn't for jprofiler, we would need to
run our stuff on 16 servers instead of 3.