plan c anyone?
2 plus ones
Shared publicly•View activity
- I thought Plan A was use-microservices, ignore-jigsaw.
Jigsaw was Plan F40w
- I'm not RedHat is qualifed to label anyone elses stuff deficient.40w
- Thanks for the redhat post and the follow up. While I agree with the follow up that the redhat post is probably biased, my humble opinion is that the follow up is showing the benefits of the tools in javase while redhat focuses on the shortcomings of jigsaw in JavaEE which is way more critical for me. And I think it's clear to everyone that in recent years Oracle has been working a lot on javase without caring that much about JavaEE. What worries me most is the long list of issues when working with maven. The redhat post was signed also by sonatype engineers, and I trust their opinion to be less biased as maven is not tied to osgi or jboss modules. I am afraid we will need to wait ages for JavaEE 9 or it may happen that JavaEE 9 will be skipped and we will have JavaEE 10 when some of the issues will be solved by javase 10. Long story short: future does not look good for JavaEE developers, who historically always had to use older versions of Java for several years and now it may be even worse.40w
- Me, ive moved to typescript and inversify.40w
- The maven issues described seem wrong. With jigsaw we still need maven to define the specific artifact with version and can still use exclusions etc. Sure, jigsaw enforces tighter compile time rules but i don't agree with their 'maven issues'.39w
Add a comment...