Using Java 9 Modularization to Ship Zero-Dependency Apps
This is definitely an improvement for Java, but it leaves me with a few thoughts as someone who has done Java professionally at times, but also professionally lived in other ecosystems including C++&#x2F;Qt, Python, Ruby, Golang, and of course node&#x2F;JS.<p>1.  Setting up a project is still a pain in the butt.  Tools like Gradle are a nice improvement over Ant (and some would say maven), but still most people don&#x27;t even understand them.  You have some serious reading ahead of you if you want to set something up that isn&#x27;t already templated somewhere for you.  You can lean on an IDE for sure, and for most Java devs this is probably a no-brainer.  I&#x27;m weird in that I don&#x27;t like magic.  I prefer to know what the tool is doing on my behalf, and the Java IDE world is so complex that it isn&#x27;t practical to learn that unless you&#x27;re in the ecosystem for years.  Then dealing with weird exceptions from the JVM can be maddening.<p>2.  The Java world moves slowly.  It could reasonably be years before many shops transition to Java 9, when you would actually realize the benefits of this in your work life.<p>3.  So much Java runs on the server side anyway, where executable size and entrypoint doesn&#x27;t really matter that much.  Because of this, it may only be a small subset of Java shops that really get into Java 9&#x2F;Jigsaw and iron out the bugs, and create tools&#x2F;tutorials for others.