41–50 of 147 posts
> Amazon Corretto is a no-cost, multiplatform, production-ready distribution of the Open Java Development Kit I really, really wish AWS would start using practical/self-explanatory names for their products.
So like "Java" and "Swing"?
> Amazon Corretto is a no-cost, multiplatform, production-ready distribution of the Open Java Development Kit I really, really wish AWS would start using practical/self-explanatory names for their products.
I’m honestly surprised they didn’t go with “Simple Java Service”. /s Edit: Added sarcasm indicator
> Amazon Corretto is a no-cost, multiplatform, production-ready distribution of the Open Java Development Kit I really, really wish AWS would start using practical/self-explanatory names for their products.
I’m honestly surprised they didn’t go with “Simple Java Service”. /s Edit: Added sarcasm indicator
Earlier quoted context omitted.
Lack of long-time support commitment. A lot of java users want to hear someone say "we'll push updates for any and all CVEs for the next forty-two years, and that's a promise". They may not actually install those updates, but they want to hear someone say that they will exist.
But isn't it exactly what Oracle offers? For the money, of course.
Earlier quoted context omitted.
I'll take names over alphabet soup. My EBS EC2 machines are not playing nicely with ELB (but my EFS ones are), I think it might be to do with EMR, or maybe EKS.
You could always say: "My elastic block service elastic cloud compute machines are not playing nicely with elastic load balancers (but my elastic file system ones are), I think it might be to do with elastic map reduce, or maybe elastic kubernetes service." No soup.
Earlier quoted context omitted.
As of JDK 11, there is feature parity between OpenJDK and Oracle JDK, which is the JDK that most people used until now. In JDK 8, the Oracle version had several closed source additional features (such as Java Flight Recorder and the Z garbage collector). Also, implementations of things like graphics rendering used to be different in Oracle JDK 8 and earlier. That's no longer the case. Oracle JDK and OpenJDK should be…
Amazon's OpenJDK is 1.8.0 which is JDK8, so it still 'misses' those Oracle's closed features?
Here's a good stackoverflow post on the topic (note this is about openjdk 7). Things have only improved since then.
https://stackoverflow.com/questions/11547458/what-is-the-dif...
If you are doing any kind of server side deployment, openjdk has been a drop in replacement since the java 7 days. Essentially all linux distributions include it and you have to jump through hoops to get the oracle version.
There are differences between different openjdk builds though. I've ran into issues with certificates a couple of times on Ubuntu. Also they had a strange notion of what is stable and what is not early in the life of java 8. Another issue is the licensing of the test suite. This makes it hard to test your builds. The words certified build, implies that the produced build passes the licensed test suite.
Expect an article by Ben Thompson on stratechery.com in the next week.
Legitimate question: what is keeping stock OpenJDK from being considered "production-ready" as it is?
Lack of long-time support commitment. A lot of java users want to hear someone say "we'll push updates for any and all CVEs for the next forty-two years, and that's a promise". They may not actually install those updates, but they want to hear someone say that they will exist.