Gosling, OSGi, Jigsaw and Shenanigans

i read an article where james gosling comments on osgi and jigsaw, here’s what i found:

according to james, osgi is:

• from a different universe
• kind of huge
• doesn’t play well in the smaller spaces

so… i’m sorry, all due respect to james but i’m going to have to call shenanigans on this one.

why? well, let’s go through his three points.

first, gosling claims that osgi is from a different universe . i’m not sure which universe he’s referring to, but osgi has been around since 1999 (in fact, the osgi alliance was founded in march 1999). osgi initially targeted things like set top boxes, mobile, automotive and the home automation market. if you look at the osgi membership , you see the diversity of companies involved. about 5 years ago, osgi moved into the desktop application space via eclipse and the rich client platform (rcp). now you see companies building applications on top of osgi. here are some examples:

• nasa loves eclipse/osgi
• ibm’s lotus notes ecosystem is now powered by eclipse and osgi
• the swiss railway system is managed by eclipse and osgi
• sap commits to eclipse and osgi

a couple years ago, osgi started to move into the server and enterprise space. now, i can’t find any major application server that doesn’t use osgi under the covers. from ibm’s websphere, glassfish to springsource’s dmserver.

so on the contrary james, i believe osgi is well entrenched in the universe we live in . in fact, osgi has continued to evolve since its inception, the specification didn’t come out of nowhere.

second, james claims that osgi is kind of huge . i’m not sure what he means by this, there are various flavors of osgi that come in different sizes based on your needs:

• eclipse equinox (1100 kb)
• apache felix (360 kb)
• concierge (80 kb)
• and so on…

i wouldn’t call any of these implementations huge. if osgi was huge, you wouldn’t see companies like buglabs power their bug device to enable modularity for building cool little devices :

finally, james claims that osgi doesn’t play well in the smaller space . well, as we saw with the bug example above, that’s obviously not true. if you look at the history of osgi, james’ statement is ludicrous as osgi’s initial mission focused on the mobile and embedded space. nokia and sprint have shipped phones running osgi technology. there are even companies like band xi running equinox osgi-based applications on embedded devices like the catalyst ec :

heck, you can even plug a device into your wall socket that runs osgi.

i can go on and on… so what’s my point?

if james wants to talk about osgi, he should learn more about it first, otherwise he perpetuates misconceptions that help no one. i think we all agree that modularity is a good thing for the software industry and we should be working together to push that concept forward.

on a side note, james, if you want to learn more about osgi and its history, i would gladly set some time aside to chat. i’m sure people like peter kriens and bj hargrave would do the same. you’re also welcome to attend a free osgi mini-course that jeff mcaffer and i are giving on equinox and osgi in a couple of weeks.

from http://aniszczyk.org/