I often get subtle hints from my boss that he would be happier were we developing much of our software in something much more sexy than PHP. It depends on which CEO’s and CIO”s he’s been talking to whether he leans more towards Java or MS’s .Net in a particular week. The boss will suggest maybe one or the other may become necessary as our projects move forward and this typically comes up during conversations with partners or those outside the company in a position to help out. I know what he’s really thinking, besides being embarrassed we’re not already on a popular platform bandwagon he wants to gain those few extra marketing brownie points. I don’t begrudge him thinking that or occassionally bringing up the questions as someday a complete from scratch change of language may be a good move. Just not for the next several quarters.

With all this in mind I try to keep up on the this language versus that language debate just enough to have some reserve ammunition on hand for the the next time the boss brings it up. Afterall, I’m not ready do dump that many lines of code just yet. Tonight I’m floating around my list of websites that only rate weekly visits and I find a great white paper on Dynamic Tools for Dynamic Languages over at ActiveState linked from PHP Everywhere( one of my favorite PHP/development related blogs)

PHP, unlike Perl and Python which were very broad in scope, focused from its inception on a single task: building dynamic websites. It’s safe to say that it has succeeded, with the latest Netcraft surveys finding PHP installed on over 16 million domains. PHP combines a syntax that is easy for even novice web designers to learn, with a rich library of modules that capitalize on the fact that most websites need to do similar things (talk to databases, cache images, process forms, etc.). PHP is now considered the most serious competition to the web strategies of both Microsoft (with ASP.NET) and Sun (with J2EE).

That ought to keep me out of these conversations for a month or so…

Comments are closed.