3 ms·
I'd like to see more of a rationale for not using Corretto on non-AWS servers. What's wrong with it?
by twic 5y ago
I'd like to see more of a rationale for not using Corretto on non-AWS servers. What's wrong with it?
- topspin 5y agoI had no idea anyone thought Corretto should be isolated to AWS. I've found nothing wrong with it.
- weissed 5y agoI had the same thought, what’s the reason this is not recommended outside AWS?
- distances 5y agoI'd also like to know. Even some large Android projects use Corretto.
- verst 5y agoAnd a similar question for the Microsoft build. This isn't Azure or Windows specific at all.
- bombcar 5y agoNothing - but any of the "vendor JDK" they recommend on that vendor's platform only - see RedHat for another example.
- miked85 5y agoThere isn't any rationale. The author doesn't even attempt to explain the reason behind most recommendations.
- exabrial 5y agoNot sure. The JDK works pretty well, but for whatever reason, I had issues with Corretto crypto provider and running it with Metabase. Switched to Adopt and didn't look back
- 8organicbits 5y agoThe author doesn't justify it but I suspect the thinking is related to how fixes are prioritized. If there is a bug/performance issue that only happens in the context of AWS, then Corretto would be the most likely to rapidly patch the issue as it impacts their customer base. Potentially patches for those sorts of issues would be discovered by AWS through their own use and testing. Likewise for the other vendors and their own platforms.