Hacker News Reader

Comment by fivea | Hacker News Reader

> JetBrains' attitude to this has been horrendous.

> Try running their products on a more recent JVM.

Isn't JDK17 literally two or three months old?

JDK17 was released on sep 17 2021. Meanwhile, IntelliJ 2021.2 was released on July 27 2021, and IntelliJ 2021.3 on November 30 2021.

Who in their right mind would dump a stable LTS release in favour of the latest and greatest in the middle of a point release? Specially on a production project which is expected to be rock solid, and quite possibly wouldn't be able to recover from a reputation hit caused by regressions introduced by hasty ill-advised migrations?

View on HN

JDK 11 would be fine, but why have such a bad default config for the JVM? They literally use a deprecated GC algorithm instead of the default and set a way too low max heap size (I guess so people don’t say that it uses too much RAM, but all it does is making the GC run constantly)

It's for people using 8GB ram laptops.

"more recent" does not mean "the most recent"

> "more recent" does not mean "the most recent"

JDK17 is the latest LTS release.

The previous LTS release was JDK11, which is already shipped with IntelliJ.

What, exactly, are you trying to argue?

What, exactly, are you trying to argue?

Disingenuous HN snark never stops; (re-)read the whole thread to find out what you've missed.

You literally write:

> Try running their products on a more recent JVM.

> ...

> while the policy of sticking with a version 11 JDK is to the detriment of users on other platforms.

The answer is, quote: "JDK17 is the latest LTS release. The previous LTS release was JDK11, which is already shipped with IntelliJ."

What exactly do you want of JetBrains?

Interim releases receive only 6 months of support. They'd have to switch the runtime version mid-flight, or leave users with an unsupported runtime, or dedicate a ton of resources to supporting JDK themselves (in addition to all the patches they do now).

Reply on news.ycombinator.com