An Open Letter to the JCP Executive Committee

Re:An Open Letter to the JCP Executive Committee by njitram on Friday May 05, 2017 @02:06PM (#14275507)

I never understood the need for the JCP to build a whole new standard for modularization. Why didn't they rubber stamp the OSGi spec which is used everywhere, is extremely solid, has multiple great implementations and provides stuff that this standard not even has (like runtime updating of modules, versioning and more). Felt to me like politics/not invented here syndrome from the start, no wonder there is so much pushback from the community about this standard.

[ Parent | on HN ]

Re:An Open Letter to the JCP Executive Committee by DamonHD on Friday May 05, 2017 @02:57PM (#14275937)

In my experience OSGi is horrible and unwieldy. Avoiding its complexity for this job is good.

[ Parent | on HN ]

Re:An Open Letter to the JCP Executive Committee by leastangle on Friday May 05, 2017 @03:19PM (#14276097)

Modularization itself is complex. No matter if OSGi, Jigsaw or whatever, modularization done right is non trivial. I wonder when ppl. start realizing that instead of blaming it on implementations.

[ Parent | on HN ]

Re:An Open Letter to the JCP Executive Committee by threeseed on Friday May 05, 2017 @05:02PM (#14276833)

Modularisation isn't complex at all. We have had it for years with JARs. They are simple and easy to use for everyone involved.

Sure modules of this kind are a bit more complicated but they shouldn't be significantly so. Often the JCP tends to over-engineer and over-complicate.

[ Parent | on HN ]

Re:An Open Letter to the JCP Executive Committee by threeseed on Friday May 05, 2017 @05:00PM (#14276822)

OSGi is probably the worst designed piece of technology I've ever dealt with.

If all you want is basic plugins it is horrifically complex, obtuse and unwieldy. Which is why very few people can be bothered dealing with it and just stick with Service Loaders.

[ Parent | on HN ]