What Is PHP?

The full form of PHP is Hypertext PreProcessor and is a server-side scripting language. The PHP code can be combined with regular HTML tags and parsed on the server. The creator of PHP, Rasmus Lerdorf first displayed the language in the form of a Perl script . In 1997 it was adapted by Andi Gutmans and Zeev Suraski to use a C-written compiler. They completely reconstructed the original PHP into the web language that we know and use today.

Uses of PHP

It is used in the creation of dynamic web pages. Web developers like it because of its fast parsing and flexibility and versatility. PHP is a popular tool for managing a form's data after it is submitted and comes built in with many different interfaces and API's. It has database capability built into the language, the most common database being MySQL. Typically the PHP can connect to any SQL enabled database.

The Syntax of PHP is similar in structure to Perl and C where curly braces { } define blocks of code and semi-colons specify the end of a statement PHP is as easy to learn as Perl. It maintains all the traditional loops, if/else, and subroutines that are expected in a programming language. One difference between the two is that the code'?' is embedded in with the HTML; you could however, use a separate file. The PHP code is different from HTML code by use of the opening and closing tags. When it finds a PHP file, it tells the server to scan through for these tags, and execute the code in between them. The server recognizes a PHP enabled file by its extension, .php. These are essentially HTML files with PHP codes in them.

Getting Started

To start PHP requires a server with PHP installed and a simple ASCII text editor such as Notepad or VI, eMacs, Kate, etc. for a UNIX/Linux machine.

What are the problems faced by PHP?

It is case sensitive. For example if you name a variable $MyVar, you cannot call it as $myvar or $mYvAr. In case you forget to close your curly brackets, then it helps to indent lines inside the curly braces so that any missing braces can be spotted easily.

Not long ago, a friend of mine sent me an email asking for my opinion on whether a site he was developing should be done using Wordpress, LAMP, or ASP.NET. I've used all of those, but have always been so focused on the details and learning them that I never really thought about the great question of "What technology should be used for a given site?". That is such a good question that I decided to put my thoughts on paper and help provide some education to others.

Some people don't have the skills and ability to actually be able to choose the most appropriate technology. They know one thing and that is going to have to be made to work in all cases. That's not necessarily bad, but it's nice to be able to switch between technologies based on the type of site. The important thing to realize in web site development is that one technology does not fit all.

Wordpress

I have several web sites currently running Wordpress. I originally thought of Wordpress as just a blogging platform. While that is certainly its main use and what it is optimized for, you can definitely use it to create a more "traditional" looking web site. It is very configurable and there are tons of custom plug-ins available that can allow you to add RSS feeds, SEO tags, voting, etc. Since Wordpress is developed using PHP and MySQL, it is also possible to create your own plugins and customize your site template. Oh, and that's the other incredibly awesome thing about Wordpress -- the templates! There are literally thousands of free Wordpress templates available for download. If you can't find one that fits the theme of your site than you aren't looking hard enough.

Another nice thing about Wordpress is that you can easily find web hosting providers that support Wordpress. In most cases, you can click an install link and have Wordpress properly installed on your site in a few seconds. Then you go to the Wordpress admin console and configure your site. It is all very easy. You can upload multiple templates and easily switch between them. It is also easy to make minor changes to the templates (like changing tag lines, colors, etc.).

The other benefit of Wordpress is that it is a blogging platform and the search engines love blogs. You can configure your Wordpress install to automatically ping one or more blogging services whenever you add a new post or page. That way they know your site has changed and they should come index your site again. If you want your site to be found then using Wordpress as the underlying engine is a good option.

LAMP

In case you don't know, LAMP stands for Linux-Apache-MySQL-PHP, which is a very common and powerful set of technology components used for building web sites (and did I mention completely Open Source and free!). If you want complete control over your web site, then LAMP is a good option. There are plenty of examples, free scripts, etc. available on the web site to help you get started. There are also plenty of free editors and tools to help you along. The downside of LAMP is that it is hard for you to create your own development "environment". Since most of us run some flavor of Windows as our desktop operating system, we would need to use something like VMWare or Virtual PC to create a virtual machine running Linux. The next challenge is getting all of the components properly installed. While the installers for the LAMP components have definitely improved, they still don't compare to the ease of installing a Windows-based application. The next challenge with LAMP is debugging. It would be nice if we all wrote perfect code, but the reality is you need the ability to debug. There are PHP debuggers available. A good one is going to cost you some money though.

One of the best things about LAMP is that there are TONS of web hosting providers out there for you to pick from. The reason is quite simple -- LAMP is completely open source, so it there is very little cost for the hosting company to bear. That means more margin for them!

ASP.NET

Microsoft's contribution to web site development is ASP.NET. You can use any .NET language (C#, VB.NET, Python.NET, etc.) to develop an ASP.NET based site. In my opinion, the best thing about ASP.NET is the fact you can use Microsoft Visual Studio for you development tool. Visual Studio is the best tool out there. Yes, it costs money, but you definitely get what you pay for. The other nice thing about ASP.NET is that you can easily develop on your Windows-based desktop or laptop.

It is harder to find a good ASP.NET hosting provider. Believe me, I've looked! And I've used several different ones. The ASP.NET providers lag behind the LAMP providers in terms of what they offer. You also need to be careful and really understand what the provider means by things like "host unlimited # of domains". In many cases they just mean you can have an unlimited # of domains point to your single web site. That probably isn't what you want.

I mentioned the use of Visual Studio before. That tool is awesome and makes development SOOOO much easier. I did quite a bit of development using LAMP and got some sites up and running. I used Eclipse with a PHP plug-in and it worked pretty good. I didn't have Apache running or Linux, so couldn't really debug but I still managed. When it came time to create a more advanced web site, however, I quickly decided to switch over to ASP.NET and use Visual Studio. Debugging was a snap and the coding was made much easier thanks to Intellisense and Visual Studio's ability to "import" web services and make them easier for me to call from my code.

Making the Right Choice

Each of the technology options has pros and cons. If you want to get a site up quickly and it will be displaying basic information (text, images, video) then Wordpress is a great option. If you want a more advanced web site but don't want to spend much money on development tools, then LAMP is the best choice. Finally, if you already have Visual Studio or know .NET programming, then ASP.NET is a good option. If you're really lucky and can know all three then you can use the right tool for the job no matter what.

Lex Parsimoniae is Latin for "Law of Parsimony", which pulled out into its simplest form is the The Law of what can be spared, should.

This is a theory that I have been studying for the past year and through observation believe that this can be applied to all situations that require a more efficient, functional solution. This paradigm has many names, but is best know as Occam's Razor. His razor suggests that when resources are limited or when speed of function is essential, design / complexity trade-offs should be based on what does the least harm to the probability of success, however that is defined.

Form is Function

There is a school of thought that beauty in design results in good function, but I prefer to subscribe the fact that just concentration on the functionality will by its very nature, create its own aura of design. Sometimes, the focus on functional efficiency inspires a feeling that goes beyond aesthetics and ultimately give us the sense that its form is of a higher echelon.

Barrier To Entry

The brain is an amazing piece of kit. One of its most amazing functions is its ability to optimise when processing data. Each brain has been trained over many years (or maybe it inherently has the ability) to simplify individual objects into groups. Instead of seeing each individual blade of grass, the mind sees a field. Millions of pieces of data grouped into one object because it knows, to comprehend millions of pieces of grass would take and enormous amount of effect. Effect that could be focused elsewhere. So it generalises to make life easier. This sort of information overload can happen in design as well; Too much will distract from your likely objective. Remember that 7 Second Rule? If your web app or website has 7 seconds to impress then wouldn't you prefer showing off your functional muscles? How useful your app is? and not long it takes to load the really cool (bandwidth crunching) design? Remember how it easy it is to make your mind up about someone when you them for the first time. Same rules apply.

Just Do It!

What are your objectives and goals? Hopefully, when developing a web app or website, to make your (or your users) life easier! And let's remember, this 'thing' we call the Internet is broken. So don't break any further with dodgy CSS and bloated javascript. Functional Turn Around is the most impressive aspect for me these days. Spend time developing how the app works, refine it, refine it again, then again. Then when it works, design around the edges. If you like Latin phrase then try this one:

"entia non sunt multiplicanda praeter necessitatem", or "entities should not be multiplied beyond necessity"

For more information about Occam's Razor and various other development theories, read this Design and Development Blog at www.gammatan.co.uk