3 ms·
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, i
by njitram 9y ago
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.
- DamonHD 9y agoIn my experience OSGi is horrible and unwieldy. Avoiding its complexity for this job is good.
- leastangle 9y agoModularization 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.
- threeseed 9y agoModularisation 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.
- threeseed 9y agoOSGi 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.