10 Oct 2003 nuncanada   » (Journeyer)

I gotta say i finally got deeply convinced over John Lim's post on his weblog 'Is Java more scalable than PHP?'

What it got me to wonder is how then, Java became the de facto standard for big corporations web applications?

The idea behind developing java was 'Write once, run everywhere'. But for those with lots of money (big CMSes for example), it's hardly a problem if a solution can work only in very specific servers, probably a lot more money will be spent in development... So the major moto behind Java doesnt help much in this case...

Besides, Java solutions are built to share, which makes them really hard to scale, adding more complexity on top of that.

PHP seems to take the right attack at this problem, letting the sharing part occur in databases, or 3rd party permanency servers... So what is done in PHP can scale linearly...

I think Java is much more suited for what was its original intention, to run everywhere. For example a nice editor on the web, where you would need to have big text files in memory (autosave, automatic grammar checks etc), where php solutions probably would be a bunch of hacks or impossible...

I wonder if the reason for Java in corporate web services isnt as a quote from Djisktra "Complexity sells better and the market pulls in this direction"

Latest blog entries     Older blog entries

New Advogato Features

New HTML Parser: The long-awaited libxml2 based HTML parser code is live. It needs further work but already handles most markup better than the original parser.

Keep up with the latest Advogato features by reading the Advogato status blog.

If you're a C programmer with some spare time, take a look at the mod_virgule project page and help us with one of the tasks on the ToDo list!