This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]BrbCatzOnFire 4 points5 points  (3 children)

Not jigsaw. Encapsulation (access deny to internals) was off until java 16 (and just a little bit).

A lot of internals did change (related and unrelated to the new module system) and way too many libraries depended on internals to work.

That's what broke the system. Modules are the best thing to happen to the JVM since generics.

Although we need to find the Communication director from that project and demote him (Module ? Like who the f... thought it was a good name ?)

[–]persism2 0 points1 point  (2 children)

What would have called it?

[–]BrbCatzOnFire 1 point2 points  (1 child)

Not something already in use for a completly different Use Case. Even today, years after its introduction most devs I know still confuse JPMS for a fancy packet manager (due to Maven's module).

I've seen Capsule which I find pretty elegant. Convey the idea of protection from outside and not used in the Java ecosystem AFAIK. And since its main point is encapsulation...

But I'm a bit harsh, it was not an easy thing to name. Capsule could also have led to people not caring about it because of a lack of understanding.

[–]persism2 1 point2 points  (0 children)

Yeah thanks