Running IntelliJ Idea with JDK 17 for Better Render Performance with Metal

If anyone is interested why this is even a thing, you can see here [0] how every change in the IDE repaints whole window, thus eats CPU like mad. On the MacOS with external 4k+ monitor, this really tanks even macpro, like there is no GPU acceleration at all and everything is rendered by the CPU.<p>[0] - <a href="https:&#x2F;&#x2F;photos.app.goo.gl&#x2F;fsxgEHXCsTzKL37w7" rel="nofollow">https:&#x2F;&#x2F;photos.app.goo.gl&#x2F;fsxgEHXCsTzKL37w7</a>

If you use a HDPI screen, e.g. retina, external 4-5K screen, just turn off anti-aliasing in the IDE options.<p>It renders a ton faster and you won&#x27;t see the difference, because you need anti-aliasing when 1px=1px, you don&#x27;t when it&#x27;s subpixel anyway.

Dumb question here. Why is this necessary? Does Jetbrains not include their latest Jetbrain Runtime release in their IDE builds?<p>Or maybe Jetbrains Runtime releases run a bit ahead of what gets bundled in with the various Jetbrains IDEs?

I wonder: Would the JDK17 GraalVM offer additional benefits?

JDK17 also supports wayland natively, one of the major blockers of having a good experience on wayland is waiting for the upgrade to JDK17.<p><a href="https:&#x2F;&#x2F;youtrack.jetbrains.com&#x2F;issue&#x2F;JBR-1315" rel="nofollow">https:&#x2F;&#x2F;youtrack.jetbrains.com&#x2F;issue&#x2F;JBR-1315</a>

Fwiw, I tried this w&#x2F; RubyMine 2021.3.1 RC and the menu bar items stopped working. None of them display anything now, which is quite annoying, but nor really a dealbreaker because you can Cmd + Shift + A to do anything.

It amazes me that people put up with the gigabytes of RAM and full cores it takes to use Jetbrains products when VSCode&#x2F;Vim&#x2F;emacs can do 99% of what Jetbrains IDEs can do with LSP at a fraction of the power consumed. I guess fleet is Jetbrains acknowledging this shortcoming, but paying for current products that are marginally better than free and open source seems crazy to me.