4 ms·
It isn't really but aimed at a different use case. Everyone rallied against OSGi because the strict modularity showed developers that in general their applicat
by alblue 11y ago
It isn't really but aimed at a different use case.
Everyone rallied against OSGi because the strict modularity showed developers that in general their application wasn't as modular as they thought it was; and the fact that class loaders enforced that permissioning model showed where random Class.forName and module busting code lived.
Guess what? Those developers will have exactly the same problems with Jigsaw modules.
What Jigsaw will do is educate Java developers that the pain points are in strict modularity rather than any one module system.
- needusername 11y ago> Guess what? Those developers will have exactly the same problems with Jigsaw modules. And many more. Jigsaw also locks down reflection. In addition Jigsaw lacks many work arounds that OSGi has to get software working (fragments, buddy classloading, dynamic imports, optional dependencies, capabilities, …). Honestly I have a hard time seeing any existing large code base work on Jigsaw.
- mike_hearn 11y agoNot any more. Requiring code modifications to use cross-module reflection was too painful and was dropped in the most recent Jigsaw iteration. You can reflect across module boundaries without problems now.
- needusername 11y agoEven for non-exported types?