Project Jigsaw: Complete
I don&#x27;t follow Java too closely and the world &quot;module&quot; is so hopelessly generic that I had a hard time understanding what the article was talking about.  It links to this document [1] though, which is a long read, but does an excellent job of describing of describing all the ins and outs of the module system.<p>(tl;dr Packages can now declare themselves as modules instead of simple namespaces, and they get to choose exactly what they export and what other modules they require. Projects can now resolve their types from within modules with a <i>module path</i> instead of on a per-type basis from the class path. It&#x27;s a huge step forward for Java modularity and dependency management.)<p>I have a hard time being <i>too</i> impressed because more modern languages are doing this out of the gates and with far fewer hacks and more out-of-the-box tooling (e.g. Rust), but acknowledge just how monumental of an effort it was to design the new system and then build it into Java&#x27;s core in a way that&#x27;s mostly backwards-compatible. Java&#x27;s going to be around for a long time, and this is a big long-term gain for the ecosystem.<p>I&#x27;d <i>really</i> love to see languages like Ruby tackle this next. It&#x27;s sorely needed.<p>---<p>[1] <a href="http:&#x2F;&#x2F;openjdk.java.net&#x2F;projects&#x2F;jigsaw&#x2F;spec&#x2F;sotms&#x2F;" rel="nofollow">http:&#x2F;&#x2F;openjdk.java.net&#x2F;projects&#x2F;jigsaw&#x2F;spec&#x2F;sotms&#x2F;</a>