3 ms·
Most no votes are only because they are concerned about their might with the JCP.... This is a sad day for software development. ... is concerned about the
by merb 9y ago
Most no votes are only because they are concerned about their might with the JCP....
This is a sad day for software development.
... is concerned about the lack of a healthy consensus among the members of the Expert Group
From our point of view the lack of consensus inside the EG is a dangerous sign
I understand IBM's and others reason for their "No" vote and heard many similar concerns by e.g. the OSGi community or contributors behind major build systems like Maven, Gradle or Ant. Most of their concerns are still unanswered by the EG or Spec Leads
What we are especially concerned about however, is the lack of direct communication within the expert group
We echo ... comments in that we absolutely recognize the tremendous achievements and the great work that has been carried out until now by the EG members as well as (and especially) by the Spec Lead himself.
policits will either delay Java 9 or completly kill it. some people just want to show their teeth. sad.
- lvh 9y agoHow is this politics? They raise specific technical concerns by, amongst others, the de facto package manager! Who would have to raise concerns for you to not simply dismiss this as teeth-baring?
- merb 9y agothey don't raise specific technical concerns. they want to have more time to address/disucss stuff about the specification. also maven is not the de facto package manager. the only thing which might be defacto is the publishing style, however there are many other package manager in the java world. also a lot of this stuff could've been cleared up way way earlier. p.s.: even if the one outlined is not a policitcal move, some votes definitly are.
- lvh 9y agoNone of those other package managers have had their issues (mostly the same) addressed either; it's a lowest common denominator: people are complaining that _not even_ Maven has been addressed. Even if it were true that somehow Maven isn't the de facto package manager (I disagree), it is certainly more than big enough that the JCP doesn't get to casually ignore its existence.