Wednesday, 13 May 2009

thoughts on jsr294 - v0.0.3

It's been a while since I posted some thoughts on JSR 294. I was quite vocal on the observer list some time ago but then decided that I should shut up since I am not on the expert group.

In all honesty, I find the JSR 294 mails confusing. The mails that appear on the EG mailing list (copied to the observer mailing list) seem to go round in circles and contain contradictory information, yet the spec lead seems determined push forward and still references vague and informal specifications that were published seemingly years ago, while seemingly ignoring the please of other members of the EG.

Frankly, reading the JSR mails makes me feel a little ill about the future of Java. JSR 294 is going to be a vague specification that breaks Java just enough to affect the leading module system (OSGi) in a very negative way. It wouldn't be so bad if I could see that Java would be in whole unaffected - because existing module system(s?) could just carry on unaffected and ignore the spec, but that just isn't clear.

My main worry is that 'modules' in Java will be come overly complex to achieve regardless of the module system by adding what appears to be minimal (and low-value) changes to the language.

No comments: