Thursday, November 15, 2007

Eclipse and Web Technologies

The news yesterday by Denis regarding Babel is terrific. Globalizing Eclipse through a community driven approach seems so obvious, yet somehow so novel. However, the choice of technology (LAMP: Linux, Apache, MySQL, Php / Perl / Python) caught my eye. LAMP seems to be one of the most common application stacks (the Microsoft stack being the other one).


Where does OSGi / Java / Jetty (and possibly GWT, I call this J-JOG) fit in here? Is there a reason why this configuration is not even mentioned in the alternatives section on Wikipedia's Lamp article? Is there something fundamentally wrong with this setup (scalability, performance, stability) or is it simply a matter of preference?


This is not meant to start a flame war, and I am by no means questing the choice of technology, I'm honestly just curious.

4 comments:

Mike Milinkovich said...

Ian,

In this case, the reasons are purely pragmatic. The initial code contribution is written in PHP. Our webmaster staff has mostly PHP skills. Our website infrastructure is LAMP. I don't know how many people realize this, but none of eclipse.org runs on Java...it's all LAMP.

Chris Aniszczyk (zx) said...

Sometime it's just the right tool for the job Ian.

Bull said...

Chris, I agree that in the case of Bable, LAMP is the best choice (for all the reasons Mike mentioned). I'm just trying to get a sense of if there are any technical limitations of choosing OSGi / Java / Jetty over the more traditional web stacks? And if there is anyone out there who is choosing this stack for web applications?

(I have chosen OSGi/Jetty on the server for two sites I built, but my sites only have a handful of users).

Denis Roy said...

Actually, Mike is sorta wrong ... help.eclipse.org isn't LAMP, it's Eclipse (Java/Jetty/etc)