So what you’re saying is, it’s not so much that Java support is missing from Wayland (which wouldn’t make sense to begin with), it’s that Wayland support is missing from Java.
This is technically correct, and you’re right about where the blame lies, but I suspect for most people holding off on switching, the difference is academic.
export_JAVA_AWT_WM_NONREPARENTING=1 is one of those magical make-everything-better incantations that really makes you wonder why the fuck it isn’t the default behavior
…what?
Java GUI applicatiins have to use the X compatibility layer of Wayland at the moment, because Wayland support hasn’t been integrated into JREs yet
So what you’re saying is, it’s not so much that Java support is missing from Wayland (which wouldn’t make sense to begin with), it’s that Wayland support is missing from Java.
This is technically correct, and you’re right about where the blame lies, but I suspect for most people holding off on switching, the difference is academic.
If we’re talking about “most people… switching” then IMO the real biggest factor is when their distro will decide to use it by default.
To clarify: This causes problems like ugly font rendering and some games not working, etc.
Java’s UI libraries are notorious for shoddy window handling, it also was a nightmare on X.
export _JAVA_AWT_WM_NONREPARENTING=1is one of those magical make-everything-better incantations that really makes you wonder why the fuck it isn’t the default behaviorOh i see. I thought there was more to it – but I guess it’s just Java being horrible as usual.