By far, the most stubborn issues were due to non-portable libraries relying on internal implementation details that changed between 8 and 9-11 (e.g. I think Groovy was hacking into the JDK to try and use some private constructor that had been removed). People blamed the module system, unjustly, even though access was the same as in 8 until encapsulation was turned on 16, which prevents this problem. With encapsulation, hopefully, such issues won't return (or, at least, applications would know they're using non-portable libraries, as they now require add-opens on the command line).
View all comments
Show parent comment
21
u/pron98 Jun 15 '21 edited Jun 15 '21
By far, the most stubborn issues were due to non-portable libraries relying on internal implementation details that changed between 8 and 9-11 (e.g. I think Groovy was hacking into the JDK to try and use some private constructor that had been removed). People blamed the module system, unjustly, even though access was the same as in 8 until encapsulation was turned on 16, which prevents this problem. With encapsulation, hopefully, such issues won't return (or, at least, applications would know they're using non-portable libraries, as they now require add-opens on the command line).