The case for dependencies on automatic modules

Nicolai Parlog nipa at codefx.org
Sat Apr 8 11:30:22 UTC 2017


 Hi!

Automatic modules are a great feature because they allow decentralized
and uncoordinated modularization. In an ecosystem as gigantic and
diverse as Java's that is _the only_ tractable approach!

Compared to that ability and in the big scheme of things, how an
automatic module's name is chosen is a small detail. That it might end
up preventing decentralized modularization[1] is, frankly, ludicrous and
would reflect badly on the entire modularity endeavor.

As such I am convinced that everything must be done to keep that
possible, maybe including making decisions that would otherwise not be
the way to go.

 so long ... Nicolai


[1] by not publishing modules that depend on automatic modules



-- 

PGP Key:
    http://keys.gnupg.net/pks/lookup?op=vindex&search=0xCA3BAD2E9CCCD509

Web:
    http://codefx.org
        a blog about software development
    https://www.sitepoint.com/java
        high-quality Java/JVM content
    http://do-foss.de
        Free and Open Source Software for the City of Dortmund

Twitter:
    https://twitter.com/nipafx


More information about the jigsaw-dev mailing list