In this recent post to the PHP::Impact blog, Federico talks about a slightly scary thing - a version of PHP implemented 100% in Java.

Quercus allows developers to incorporate Java code into PHP web applications and gives both Java and PHP developers a fast, safe, and powerful alternative to the standard PHP interpreter.

He mentions what it supports - things like Unicode and several of the popular extensions like APC, GD, MySQL, Oracle and PDF). There's also benefits he points out like the speed of the libraries (and safety) as well as interoperability with Java code and frameworks. Check out the official Quercus website for more information.

In a case study posted to his blog, Toomas Romer wonders if a PHP script is embarrassingly slower than than its Java counterpart.

The problem. The PHP implementation [of the IP2C library] is a lot slower. Embarrassingly slower. Without any caching the Java version is able to do ~6000 queries per second. The PHP counterpart can push through ~850 queries. The implementations are the same. The stats provided by the author of the library are 8000 vs 1200. So about the same as my measurements.

He details the script, showing what parts the script is taking up the most time on. A large part of the execution is tied up in IO and the fseek/fread and readShort/readInt functions take up a good chunk.

He even tries removing the functions and making things a bit more streamlined. This helps, but still lags behind its Java brother. Check out the post for more statistics comparing the two.

Hiveminds Magazine has a recent post about bridging the gap between PHP and Java with the help of the Tomcat add-on for Apache.

Want to run PHP and access Java? Here's how to do it on Windows XP using Apace and Apache Tomcat. Apache Tomcat is a Servlet container developed at the Apache Software Foundation (ASF). Tomcat implements the Java Servlet and the JavaServer Pages (JSP) specifications from Sun Microsystems, and provides a "pure Java" HTTP web server environment for Java code to run.

They go with the XAMPP distribution for the web server setup (for simplicity rather than on a unix-based system) and include the configuration and installation procedures to get everything up and running (screenshots included).

This recent post on the PHP::Impact blog spotlights a useful little tool for those developers needing to span the gap between PHP and Java in their applications - the PHP/Java Bridge.

The PHP/Java bridge allows you to quickly access Java classes from within your PHP classes without having to know Java and vice versa. Because of this two-way flexibility, you can access hundreds of pre-built Java classes from PHP, and hundreds of pre-built PHP classes from Java opening up your applications to greater flexibility and enhanced functionality.

The post includes an introduction to the bridge's functionality - its functions/methods, how to make a new instance of it, catching exceptions and the type conversion it automatically does (like lang.java.String directly to the PHP String type).

They also mention the Zend Platform bridge functionality for a more commercial solution.

As mentioned in This new post by Federico Cargnelutti on the PHP::Impact blog today, the BBC website is about to get a pretty radical make over - a move from Perl and static files out to a fully dynamic site made with PHP and Java.

Like most organizations the BBC has its own technical ecosystem, the BBC's is pretty much restricted to Perl and static files. The good news is that they are planning to build a new infrastructure for bbc.co.uk and roll out a new Identity platform on it. This was announced on May during the XTech 2008 presentation that took place in Dublin, where BBC's plans to reinvigorate its technical platform were revealed.

The BBC wanted to upgrade their aging platform to something a bit newer and more flexible and wanted to be able to use things like the Zend Framework for the presentation layer and a MySQL backend to power the site.

In a new post Michael Kimsal does a good job comparing the rise of PHP5 (and what it brought with it) to his language of choice these days - Groovy.

I remember when PHP5 first came out having 'discussions' with a number of people who insisted that PHP5 was way better than 4. [...] Basically, intentions were made clearer with things like "public protected private" (PPP),but I have not yet seen any web project get done faster or dare I say even much *better* due to those sorts of things. [...] This isn't specifically saying PPP is necessarily bad, but that PHP could have addressed the issue in a fashion more suitable to dynamic languages. Keep reading for an example.

His comparison is to how Groovy handles properties in a class - everything is private unless declared otherwise. This could be ported (somewhat) over to PHP and would eliminate the need to search&replace all over the code for the right variables.

In a new post to his blog Gaylord Aulke talks about some of the "soft facts" that make PHP different from Java:

Besides the usual aspects: scripting vs. compiled and in-process vs. seperate process and Multithreading etc., i think there are some "soft facts" that might be even more important for commercial software development.

He points out things like differences in object lifetimes, defined structures in applications and the "not invented here" syndrome that he thinks PHP suffers more from.

Anyway, the result is: Even though there are not so many standards in the PHP world, successful developers have a common understanding about the do's and don'ts in PHP. [...] PHP appears more predictable than other programming languages.

Sebastian Bergmann has pointed out something obvious to anyone that's ever tried to work with unit tests in PHP - there's just not that much support for it. The software is there and waiting to be used, but too many developers just don't take advantage of it.

Maybe it took the PHP community a little longer to realize the importance of testing. But now that we know how to build applications that "just work", are fast and scalable, as well as secure, a big topic in the PHP community right now is to implement processes and use techniques that help us assure that the software works correctly throughout the its lifecycle.

He points to some comments made at a recent panel discussion about PHP and testing, the proliferation of frameworks for the language and the things that have no name that developers use every day to make their code "just work".

Chris Ravensroft has posted a quick guide to getting the Java-related web server, Tomcat, up and working with a PHP installation.

Sometimes, you want to run PHP with Tomcat. Why? Well, you may have a legacy product, for instance, that will require servlets for many more years. Or you may be using this gigantic Java program and are only interested in adding a tiny PHP piece on the side.

It's a pretty simple process and most of the steps are the standard "download, install, unpack" sorts of things. The important things are the web.xml document you create and the additions to the servlet.properties file to make the PHP module work.

A little while back Matthew Turland posted about something that some developers moving over to PHP from more strict languages have an issue with - variable typing - and how its evolved in languages over time.

Without a little background in programming languages or computer science in general, it's entirely possible that typing systems are not something that have crossed your mind. I thought I'd take a blog entry to share some of my thoughts on how it's affecting the creation and evolution of languages.

He walks through history a bit, mentioning C, Java, Python and PHP and how they differ in their default type handling. He especially focuses on the "blurred line" between strong and weak typing and how some if offers special features to the language that uses the method.