Hopefully they will support Wayland in next version.
- Some graphical intensive parts (such as the markdown preview renderer) cause crashes. Turning preview off remedies this.
- HiDPI situation is garbage as usual (but that's a Linux thing in general). IntelliJ renders at half resolution so it's not as crisp as it can be, but it's perfectly usable.
- The 'everything is a window' design choice, combined with the 'you cannot click on any IntelliJ instance if _one_ of them has a window open' is worse on Wayland. This may be due to my WM of choice (Sway), but there are often prompts that are rendered behind popup windows.
- context menus have issues with immediately closing due to some mouse event. I now use keyboard shortcuts instead of mouse clicks as a workaround. As a bonus I am now discovering all sorts of shortkeys that boost my productivity.
- overall rendering performance (like input lag or scrolling FPS) seems to be worse on Wayland compared to X11, but I have not benchmarked this. May just be me being a bit too demanding/expecting from the Wayland performance promise.
To run intellij on Wayland you do need _JAVA_AWT_WM_NONREPARENTING=1 in your env. It works, but has some quirks as I wrote above.
Here's how you can test:
Run intellij; `pkill Xwayland`
or, try running intellij on a machine which does not have xwayland installed at all.
The thing is: wayland does _not_ have scaling issues, those are inherently X11 problems.
The issue which is tracking this: https://youtrack.jetbrains.com/issue/JBR-3206
I also just ran this and watched for Xwayland to spawn, killed Xwayland and it died.
Does anyone know why they do that? It’s pretty annoying even without wayland as I regularly have DataGrip, 2-3 Rider instances, and WebStorm open.