On the LearnComputer.com site there's a new post comparing the benefits/downfalls of online versus classroom learning of PHP development. They list a few advantages and disadvantages of each.

There can be many factors in the decision to learn PHP online or to take a class in-person, and for some, this can be a difficult decision to make. This article discusses the pros and cons of each method of PHP training to help you find the learning method that is going to suit your needs best. PHP isn't a new programming language, and there is a wealth of information on it on the web for every level of proficiency. The question is whether these resources alone are sufficient to get you up-and-running with PHP quickly.

For the "online" section advantages include flexible schedules and more up to date content. The disadvantages are things like a prerequisite knowledge of using computers/the training software and that the instructor might only have "set hours" to answer questions and offer help. The "classroom" option advantages include the motivation of a regular meeting time and fewer technology hurdles to overcome. Disadvantages include the need for a time/in-person commitment and that the focus might be higher level than needed to appeal to a more mass audience.

Doug Brown asks a question on his blog today that is coming up more and more, especially on those programmers new to the language that don't quite get what frameworks really have to offer. Do you really need a framework for writing PHP?

The simplicity in using PHP sometimes acts against it. Since there are very few coding restrictions, developers tend to write a bad code. The answer to this is definitely to use a framework. There are various PHP Frameworks available today like Zend Framework, CakePHP Framework and CodeIgniter. They provide a strong organization for your application and follow the commonly used MVC pattern.

To help out those new to frameworks, offers a few things they have to offer that normal procedural/library-based development may not. These include maintaining code standards, attractive URLs and getting help when you need it from other developers using the same system.

Justin Silverton has posted a comparison between PHP and Perl, with the first part coming more from the PHP side comparing it to Perl and the second the opposite.

He starts off with some of the differences between the two langauges, including that PHP was made for the web, Perl was not and that PHP scripts take less overhead for the web server to run that Perl scripts as CGIs. There are also four larger topics that he looks at:

• PHP has separate functions for case insensitive operations
• PHP has inconsistent function naming
• PHP has no lexical scope
• PHP has too many functions in the main namespace

All but the top item (that one could be argued either way) are reasons that a Perl user might cite against using PHP. For each of the items, there's a bit of description following to give you a better idea where they're coming from.