当每个人都对OSGi进行标准化时，为什么Sun会发明另一个模块系统？ [英] Why is Sun inventing another module system when everyone has standardised on OSGi?
问题描述
Sun正在投入大量精力，以 Jigsaw 的形式模块化JDK，并暗示它应该是其他Java开发人员的首选模块格式。使用它的唯一值得注意的参与者是NetBeans（和衍生应用程序）。
Sun is putting a lot of effort behind modularising the JDK in the form of Jigsaw, and insinuating that it should be the module format of choice for other Java developers as well. The only notable player who is using this is NetBeans (and derivative applications).
另一方面，业界已经围绕OSGi进行了标准化，所有主要应用程序供应商将他们的运行时基于模块平台，甚至是Sun自己的Glassfish。甚至还有一个NetBeans端口使用OSGi作为模块系统而不是NetBeans自己的模块。甚至Maven也在努力成为一个OSGi运行时。
On the other hand, the industry has standardised around OSGi, with all of the major application vendors basing their runtimes on the module platform, even Sun's own Glassfish. There's even a port of NetBeans to use OSGi as the module system instead of NetBeans own modules. Even Maven is working towards becoming an OSGi runtime.
它只是NIH，许可还是其他原因？
Is it just NIH, licensing, or another reason?
推荐答案
优秀的问题。我的理解是，在某些领域，OSGi超出了JVM模块所需的范围（带来了所有相应的复杂性），而在其他领域，它还远远不够。所以他们之间有很多重叠，但可能还不够。
Excellent question. My understanding is that in some areas OSGi goes way beyond that which is necessary for JVM modules (with all the corresponding complexity that brings) whilst in other areas it doesn't go far enough. So there's a lot of overlap between them but perhaps not enough.
这篇关于当每个人都对OSGi进行标准化时，为什么Sun会发明另一个模块系统？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
