The difference between PHP and ASP is that ASP is a Microsoft product based on visual basic syntax whereas PHP has C and Java based syntax. ASP works better on Microsoft servers.

He describes the target audience for each language and talks about the environments that they work best in as well as some general statements about their speed and flexibility. Basing his judgment on the facts he noted, he suggests PHP as the best alternative of the two for being more flexible, running in more places and being a bit faster overall.

I do have some definite thoughts on the layout of development environments. And I find that there's a huge lack of information about this on the interweb, so here you go. We use Linux, Apache, PHP, and subversion in our development environment and so these instructions will be biased towards these topics but I think you can apply this method using various other technologies.

He talks about setting up the environment for multiple developers (with advantages and disadvantages) as well as the directory layout and subversion repository setup. There's not any configuration file examples here, but its a good overview of how things are set up in his environment to make a plan of attack for yours.

In anticipation of my talk at PHP Quebec 2009 I've been going over my slides and thinking about what I'm going to update for it. One little nugget I'd thought I'd share is one way of handling having multiple environments your code must run in.

It uses a PHP variable in the $_SERVER superglobal - a custom one, APP_ENV - set by the application and checked to ensure global options are correctly set.

The more I thought about it though, the more I realized there had to be a better way. My current setup doesn't allow me to do things like test PHP 5.3 without setting up a whole new server just for that purpose, or maintain an environment like my production server.

He was looking for something that would work on a laptop, allow for easy environment switching and let him work on multiple projects at once. He came across the VirtualBox software and adapted it to his own needs (including shares folders between instances and multiple instances running Ubuntu) on his local machine.

When faced with the alternative between an off-the-shelf CMS or a custom development, many companies pick solutions like ezPublish or Drupal. In addition to being free, these CMS seem to fulfill all possible requirements. But while choosing an open-source solution is a great idea, going for a full-featured CMS may prove more expensive than designing and developing your own Custom Management System.

He breaks it up into sections that look at the hidden costs behind custom development, what components it takes, the environment to build in and some of the fundamental questions you need to ask before even getting started.

During my Dojo and ZF webinar on Wednesday, Pete Higgins of Dojo fame noted that I could do something different and better on one of my slides. This particular item had to do with how I was consuming custom Dojo build layers within my code. I contacted him afterwards to find out what he suggested, and did a little playing of my own, and discovered some more Dojo and javascript beauty in the process.

The improvement replaced the need for a manual commenting/uncommenting of an addLayer call with a bit of namespaced layers that, based on the environment, adds a dependency for the right file. One less manual process, one less thing to go wrong on deployment.

Because the Web "environment" is so diverse and contains so many forms of programmatic content, input validation and sanity checking is the key to Web applications security. This involves both identifying and enforcing the valid domain of every user-definable data element, as well as a sufficient understanding of the source of all data elements to determine what is potentially user definable.

They note that the root of most problems is input validation - most applications either just don't do it or do it poorly. They include a few tips on first security the environment the application is running in (like checking the HEAD/OPTIONS values and ensuring you're only allowing known file extensions and directories). They also mention the insecurity behind HIDDEN form elements and some issues surrounding user authentication.

The first part of this article, "Real-World PHP Security", appeared in the April 2004 issue of Linux Journal and covered the subject of secure PHP development. This article takes you, the professional PHP developer, one step further, by providing detailed explanations and reliable source code that illustrate the steps to follow in order to develop successful PHP applications.

He mentions some key issues - like keeping a clean environment and correctly using database connectivity - that can keep your application running smoothly.

Today I'm going to look at a local development server and its PHP configuration, as well as some of the IDEs/editors available for Linux, especially the cross-platform options.

Tools mentioned this time include things like a local development server (invaluable) some PHP configuration tips and the editors they mentioned, things like Aptana, Eclipse and Zend Studio.

Specifically, I will describe how I boot my PHP scripts and why I boot them the way I do. Part 1 shows how my requirements for code portability and maintainability influence the boot process. Part 2 will go into more detail about the specific steps executed by the boot code.

His basic task for the first example is to make a templating sort of system, calling a Navigation class to output links in list items. He outlines the goals of the project, what he's found for his current solution and some alternatives he's discovered along the way.