Martin Lippert's recently announced move to SpringSource is one of the most exciting events to happen in software so far this fall.

Speculation - Good Things that May Now Happen:

  • Fills gaps in OSGi and STS development at SpringSource
  • Many half finished pieces have prospect of now being glued together in a nice fit.
  • Critical last mile issues such as training and taking OSGi to the market, are now within reach. 

 

Martin Lippert is a Best Choice for SpringSource

  • Martin is a strong leader in Eclipse, OSGi, and agile.
  • Martin leads by doing and training, not just pontificating.
  • Martin has strong ties to many related groups.
  • Martin Lippert is a closer.

 

A Closer:

The word "closer" is from other industries, but it applies doubly here. A closer is someone who finishes things, gets the deal done. There are many great players in many great fields who still rely on others to close or finish the final details, and the closers are the true heroes, in some eyes.

A closer makes it really happen. He doesn't just start things. He finishes them, such as Lippert's "last mile" hooks to Spring OSGi from within Eclipse. Only when something is finished and usable does it mean anything to the world of products and deliverables.

Linus Torvalds is one such example of a closer. Many people had worked on the vast array of pieces that became Linux, but Linus closed the loop - finished that last mile. Stallman gets pissed about this, but the closer is what made Linux happen in 1991, not 1998.

Martin Lippert is a closer. Look no further than his accomplishments to date.

Evidence of Capabilities.

Each of these is just a tip of the iceberg, of course.

The Promise of Spring

The promise of Spring has always been ease of use, but recent years have seen some over-reaching in the push for SOA in a JVM modularity.

Rod Johnson correctly perceived years ago that modularity and OSGi are handmaidens to the Spring Framework. One day you will simply declare your new module, write the functionality, and wire it in declaratively and effortlessly as a completely self contained and versioned service.

This promise has fallen on hard times of late. It appeared to be a bit more challenging than the SpringSource team was able to promptly deliver - at least in terms of tooling and ease of use, and the market never materialized, because the market never saw what was possible.

Further blows ensued when developers assumed that giving Spring OSGi and DM Server to the Eclipse foundation was merely a way for Spring to walk away from it's investment. This wasn't the case, but impressions sometimes endure beyond the reality that follows.

Maybe some of this will transition to a resolved issue, with Mr. Lippert's arrival.

How Does Rod Johnson Do This?

It's a puzzlement. How does Rod Johnson do this?

Again and again Rod Johnson seems to bring together brilliant and motivated players who could easily burn up in other environments, and allow them a place to flourish. Folks with large egos, brash opinions or outspoken manner, and sizable accomplishments to match. Take these, for example - for just a sampling of recent history.

It's a credit to Rod to be able to pull this off, year after year. Any success SpringSource finds as a result, is well deserved.