On Tue, Dec 5, 2017 at 5:48 AM, dalibor topic <dalibor.to...@oracle.com> wrote: > On 04.12.2017 22:56, David Lloyd wrote: >> >> saying "Here it is, it's all done, what do you think?". I've >> certainly never had opportunity to try it out: given its status as an >> incubating module present only in OpenJDK, the only people who are >> really in a position to try it out are those using OpenJDK (as opposed >> to other JDKs) > > That's not quite correct. The jdk.incubator.httpclient module is part of > Oracle JDK 9, as well. It has been part of the JDK 9 Early Access builds > since about a year ago, afaik. The Early Access builds can be found at > jdk.java.net, fwiw.
Sure, but that's all the same ecosystem. An organization tied to, say, the IBM JDK won't have access to these. >> But those who are best able to make this kind of determination >> are those who need to be able to immediately use the API, and rely >> upon it indefinitely (for good or bad), which is definitely not the >> case for anything incubated in the OpenJDK project. > > This seems to be a more general criticism of the incubator module mechanism > as defined in JEP 11, rather than directed at this API specifically. It > wasn't raised on jdk-dev when JEP 11 was discussed about a year ago, fwiw. Of course; sometimes a thing must be tried before the weaknesses are apparent. If we all designed perfect things from the start, we wouldn't need standards and evolution. :) -- - DML
