EDIT: To be clear, those quirks would exist on your production deployment running java 1.x which is why they may be important to emulate.
So if your corporate overlords allow the IDE itself, you're good.
This is a big part of it.
If you want support for older JDKs, you have to pay Red Hat for OpenJDK support. Which isn't even "real" Java, in the eyes of many companies.
Add in the clamour of major libraries and platforms pushing everyone to go to Java 8 so they can slash great chunks of boilerplate code and it's a smooth ride downhill.
From the above site:
* Direct access to secure versions of older releases of Java SE via My Oracle Support
* Rigorous and on-going regression testing and fixes for EOL’d versions of Java SE
Because of that, Java 8 is supposed to be a smaller shift than Java 5.
No they are not, as they make use of invokedynamic. Certified JVMs must make use of the opcode and not generate anonymous nested classes, as many think they translate to.
But you're right that certified Java 7 VM must have an invokedynamic opcode.
I realize that Hacker News skews toward a different industry segment, and it's hard for people outside of the enterprise to fully grasp its horrors. But believe it or not, expecting the current version of Java to be installed on a Java developer's machine is actually a pretty big shift!
I should note that this JDK 8 migration is for EAP releases (ie early alpha/beta versions of the next major release) and that all installers (windows, osx and linux) offered by Jetbrains come with its own JDK bundled in the installer. So if you happen to work in one of those corporate environments, if you manage to get permission to run this IDEA version, you also get the required JRE to execute the ide included.
Or is your question about how JetBrains expects to get permission from the pointyhair bosses to purchase the new IDEA version for their developers in the first place? If that's your question then it's not really JetBrain's business if megacorps decide developer productivity is not worth the money to spend on buying a new copy of IDEA.
Nothing about the actual specific topic, which is that one of the most prominent development tools in the Java ecosystem now expects the current Java version to be installed.
Expecting the current version might sound mundane to a Rubyist or Node person (and it might sound like a pipe dream to a wistful Pythonist!). However, it's a pretty big change in the Java world. Backwards compatibility is highly prized...and tool or library authors have always been reluctant to use current language features, for fear of excluding users stuck on old versions.
Back when I was working in "the enterprise world", it wasn't unheard to see shops still stuck on 1.4 long after Java 7 had been released. Up until a few years ago, it was sometimes still a big deal for libraries to start incorporating generics (introduced with Java 5 in 2004).
Java 8 was SUPPOSED to an even bigger shift than Java 5, with an even slower adoption rate. However, for some reason it feels like the opposite is proving true. I'm seeing tools and libraries move to Java 8 shockingly soon compared to past experience.
I wonder why this is. Perhaps after the rocky Java 5 migration, large companies embraced the practice of updating their deployed versions more frequently? Maybe it's Oracle releasing new Java versions every two years now, and being more aggressive about end-of-life'ing the prior versions? Or perhaps it's just that I've been out of the enterprise environment and working for startups instead these past several years, and the situation in large companies is still as conservative and outdated as ever?