I have been using JSP for many years, and extensibility usually makes the face value of a monthly placement more than worthy. However, if you need to supply a basic informational or renewed page type, you probably will not need JBoss or some other sledgehammer.
With JSP / Java, it opens the door for using Java at the controller level (you probably already used or heard about the extended connection pool, distributed caching, scheduling via Quartz, Hibernate object / relational persistence). And then you can run Java on any machine with the JVM. The JSP syntax is not incredibly complex, although it does have a learning curve. As for hosting, eatj.com is still pretty good.
On the PHP side, you can easily incorporate community features like Wordpress. Although you can use nWordPress for Java, it's just not the same. Facebook, probably one of the biggest PHP implementations, uses HipHop and dramatically reduces CPU requirements.
It may also be easier to bundle work with PHP developers in your project, as they are relatively easily accessible than JSP developers. I would say, recognizing JSP and / or Ruby - it opens a few more doors, and you can end up choosing one method over another.
bphilipnyc
source share