4 ms·

Open Jdk tends to create random and strange issues. At that point you might as well pitch migrating the tech stack to .net

• yjftsjthsd-h 5y ago
  That would be somewhat odd; isn't Oracle building off the openjdk as well? And I have trouble crediting the idea that moving to openjdk is anywhere near the effort to move to a completely different language+platform, even if there are differences.
  • offtop5 5y ago
    To be fair I haven't seriously touched java in about 4 years. I do remember Android studio explicitly warning users to avoid Open Jdk My second point was a joke, still I wouldn't be the one to rock the boat. If anything is even slightly off after switching to open JDK you'd need to justify it
    • yjftsjthsd-h 5y ago
      > I do remember Android studio explicitly warning users to avoid Open Jdk Once upon a time maybe, but today: > A copy of the latest OpenJDK comes bundled with Android Studio 2.2 and higher, and this is the JDK version we recommend you use for your Android projects. - https://developer.android.com/studio/intro/studio-config#jdk https://developer.android.com/studio/intro/studio-config#jdk > If anything is even slightly off after switching to open JDK you'd need to justify it "We don't have to license it from Oracle" should justify a lot.
      • offtop5 5y ago
        I'll admit when I'm wrong. Thanks for the info
• pjmlp 5y ago
  Except that since several releases Oracle Java is basically OpenJDK + Support.
  • p_l 5y ago
    And some of those issues show up when migrating to recent Oracle Java, too.
    • pjmlp 5y ago
      Depends what you mean by recent. For me recent means JDK 14 or later.