Life at Eclipse

The party at the “P” last night was good fun. In all the years (almost 30) that I’ve been going to the Prescott, I never knew they had a party room upstairs. We’re going to have to find an excuse to use that again.

Here are a few more articles that I’ve seen on the birthday:

• AD Trends
• Alan Zeichick from BZ Media, and
• InternetNews

.

So five years ago today was when the download servers were turned on in the basement of the IBM OTI Labs on Queensview Drive in Ottawa.

It’s been one heck of a ride. I don’t think that anyone could have predicted the success that Eclipse has enjoyed. Thanks go to all of the project leaders and committers on the Eclipse, Equinox, PDE , RCP and JDT projects who made this all possible. Without your original vision, brains and hard work this entire phenomenon would have never happened. For all of you that have been with Eclipse since the beginning, a special thank you for your contributions. I hope you’re enjoying the impact that your software is having on the industry.

Thanks also goes to the Eclipse community. Eclipse has been embraced by so many: open source developers building their projects on Eclipse, the commercial ecosystem which has adopted Eclipse as the safe choice to build their products on, and the millions of developers who use Eclipse for their application development. I am constantly amazed at the energy and enthusiasm that comes from all of you that make up the Eclipse ecosystem. You are what keeps Eclipse the happening place it is.

Looking towards the future, I am excited to see what the next five years will bring. Today I see at Eclipse many very interesting new projects which have a ton of potential. There is a whole new generation of committers and leaders who will help define our future. Eclipse’s origins may be with our eponymous Java IDE, but the future of the community will be areas as varied as device software to SOA, from PHP to Ajax. (Space prevents me from listing all the projects I would love to mention.)

There has been some very nice coverage of the birthday in blogsphere and in the press today. Here’s a sampling:

• Peter Coffee and Darryl Taft, eWeek
• CNET
• SearchWebServices
• ComputerWorld

I’m looking forward to seeing everyone at the Prescott tonight for the Ottawa birthday party. I’m going to play my usual Tuesday night hockey game so I will be getting there a little bit late.

P.S. So far we have over 1300 signatures on the birthday card. Don’t forget to drop a line there and give your own thanks and Happy Birthday!

This is pretty exciting news. Motorola is going to throw its resources behind ensuring that there is an Apache-licensed Java ME implementation.

And how’s this for a quote from Mark VandenBrink:

We see industry fragmentation and proprietary software models as an obstacle to unharnessing the full power of innovation in the mobile Java ecosystem. We believe developers, customers, partners and the industry at large will benefit from a new open source model…”

Coupled with Motorola’s announcements earlier this year on mobile Linux and joining Eclipse, it seems that they have really seen the open source light.

One obvious question which is not explicitly answered by the press release is whether Motorola is going to contribute directly to Apache Harmony. I certainly hope so, as that would be the most obvious way to move forward. Harmony already has a functioning community and project, and setting those up are non-trivial exercises. Like I’ve said before, “…emulating Apache would just be dumb. Don’t emulate it. If you like their approach, just open source Java at Apache.“

Life in the Java world could get very exciting if we end up with a Sun-controlled Java implementation under the CDDL and a diverse community working on Harmony. Compared to where we were a year ago, that sounds like a major improvement.

Of course, since Sun has been promising to open source Java for a while, this Motorola announcement begs the question “why”? I think that the answer is pretty simple: licensing and governance matter.

Inspired by Donald’s post I am going to use a combination of wild hyperbole and question marks in my blog titles for a while.

Last December Onno Kluyt kindly asked if I would come and talk about Eclipse at the JCP’s Executive Committee meeting. The last point in my presentation was “JSR277 is just weird“. Apparently Peter Kriens feels the same way.

Peter has done a great job describing the technical limitations of the JSR. My concerns are related but different. It seems pretty obvious that JSR 277 exists to take some of the wind out of OSGi‘s momentum, and to ensure that the core component architecture used by Java applications is written by Sun. To even further muddy the waters, there exists JSR291, which is basically going to but a JCP stamp on the existing OSGi standard.

The problem as I see it is that whenever JSR277 sees the light of day it is going to be built into the core of JSE. This will likely happen two or three years down the road. In the meantime, OSGi exists today and there are tons of companies who are currently making large investments in products and applications built on top of Eclipse Equinox, Apache Felix, ObjectWeb Oscar, GateSpace’s Knoplerfish, or ProSyst to name just the OSGi implementations I know of off the top of my head.

When a version of the JSE ships which has an inferior and incompatible component architecture in it, it is going to be one heck of a train wreck. The combination of NIH with too little, too late is not a good one. My guess is this could end up making the JDO/EJB/POJO persistence battles of recent memory look like a pillow fight by comparison. Which is really too bad. Simply adopting OSGi R4 for JSE would have been such a bold and unifying move.

In case you haven’t noticed, the Ottawa birthday party is going to be at the Prescott! By pure conincidence, one of my favourite watering holes.

Mmmmm…Square pizza…Quarts.

RSVP at birthday-ottawa at eclipse.org