Skip to main content

What's your view of the proposed removal of Project Jigsaw from Java 8?

It's a good decision: the most important thing is to deliver Java 8 on schedule
23% (103 votes)
Java 8 without Project Jigsaw is pretty useless; Java 8 should be delayed until Jigsaw can be included
29% (131 votes)
Project Jigsaw is so late it's becoming irrelevant; developers should just use other modularity technologies like OSGi
20% (87 votes)
I don't know
12% (53 votes)
Other (please leave a comment)
16% (71 votes)
Total votes: 445

Comments

Re: What's your view of the proposed removal of Project ...

Project Jigsaw was already too late when it started, and having it part of Java 9 means that only developers that can actually use this version can take advantage of it. That means adoption will take a long time. OSGi is here, it is proven technology and it works on any JVM out there.

Instead, Oracle should focus on two things:

  1. Modularizing the class libraries. This is not that difficult at all. Apache Harmony basically already did it for them. The benefit of modularizing these is that you can choose to not even deploy the parts you are never going to use and, maybe even more importantly, you can choose different implementations of the same module (more focussed for example on embedded or server usage).
  2. Implementing "Isolates". This is also something that was already done years ago in the Sun Labs, even though it never made it to the main stream JVM. Isolates allows you to manage modules better, forcefully stopping them or limiting their resources.

Re: What's your view of the proposed removal of Project ...

I'm quite undecided... Java 8 has a lot of cool features (mainly Closures) that are well worth getting out of the door as soon as possible. But still it's a pity that Jigsaw won't make it on time. The Java community has been longing for a solid module system for so long; it may seem stupid to delay it even longer, but OTOH we've been living without it for so long, that it may be better to wait even longer and then get a really future-proof solution that can be integrated into everything else. Remember Java logging? Not really being adopted widely, is it? Although it's okay for most use cases... but such things have to really be better than the existing stuff... and it just takes some time to get it really right.

BTW: The link from the blog to the poll is wrong.

Re: What's your view of the proposed removal of Project ...

Thanks for noticing the broken link in the blog, rdohna. I fixed it.

Re: What's your view of the proposed removal of Project ...

Jigsaw requires some changes to applications (creation of modules, modules libraries, build,...), so it doesn't matter so much that it is the same package as the current JDK/JRE or not. What matters is that when it is ready it is made available in some sort so that the ecosystem starts adjusting. So probably it should go like JavaFX2 (separate, then along side, then, hopefully, within).

Re: What's your view of the proposed removal of Project ...

As far as I can tell the whole point of Jigsaw is to modulize the jre itself, not to modulize user code.

It is essential to modulize the jre as soon as possible because it makes all future code added to the jre more efficient.

Modulizing the jre will massively decrease loading time and memory use for the majority of java applications, everyone should be pushing for Jigsaw as soon as possible.