[fmw]

That is what I meant when I said that Oracle is mostly creating a nuisance for the server market. It forces sys admins and developers to jump through more hoops to get the software running on their servers (as well as to keep it updated in large deployments!). That is, those that really need it, because I'm sure some people will just switch to the OpenJDK instead, because it isn't unsuitable for production use either.

[sylvestre]

Please give me bug reports which shows that openjdk is not ready for production. I will be interested to report them upstream.

[Silhouette]

The trouble with this sort of argument is that it's not always clear what the bug is, only where it is.

For example, I work on browser-hosted user interfaces that sometimes rely on Java applets. I don't know why an applet frequently doesn't work with IcedTea. All I hear back via customers-of-clients is "Your interface doesn't work on Linux".

The advice to uninstall IcedTea and replace it with Sun's (OK, Oracle's) version is now as routine to our client's support people as telling someone with Windows troubles to reboot was a few years ago. That answer has a 100% success rate with these "bugs" so far, so I don't suppose those support staff are going to change their policy any time soon.

As a software developer, I appreciate that this is not at all helpful to those working on OpenJDK/IcedTea. However, as a guy whose rent is paid by what he earns from his clients, I can't recommend that anyone use IcedTea for anything until its well-deserved (in our experience) reputation for poor reliability is addressed.

[fmw]

I was using a double negative, so I never meant to or did say that OpenJDK isn't suitable for production. Apologies for the confusing phrasing if you misunderstood me, but I was stating the opposite of what you seem to have assumed.

[mattdeboard]

I know that it definitely does not play nice with ClojureScript. Not sure where the error is on that one, whether with CljS or OpenJDK.