Java aplications and old applications must use a backwards compatibility layer that can cause flicker and bad font rendering.
There have been efforts to provide better support for Java applications on the Wayland. For instance, the OpenJDK project has been making progress on implementing native “pure” Wayland toolkit integration not dependent upon XOrg/X11 or XWayland.
but not all toolkits support it natively and few are easy.
There have been significant developments in providing native support for Wayland in various toolkits. For example : Clutter, GLFW 3, SDL, GTK 3.20+, QT5+, EFL, Slint, Iced & OpenJDK. Just to name a few.
While it is true that not all toolkits have full native support, ongoing work is/has largely shifted towards much better Wayland support.
Wayland is a communication protocol that specifies the communication between a display server and its clients, designed to be a replacement for the X11 window system protocol and architecture.
I might be a little nitpicky here, but I feel it’s an important distinction to make as there is no single common Wayland server like Xorg is for X11.
A display server using the Wayland protocol is called a Wayland compositor, as it additionally performs the task of a compositing window manager.
Xorg on the other hand is basically one fat display server designed like a house of cards that everyone uses.
All he did was repeat shit that we’ve known for years in the most sensationalist way possible so he could get a fucking profit of a clickbait article.
He’s a “journalist”, wtf do you expect. This is his entire deal; repeat already well known shit, sprinkle in some sensational nonsense, do zero due diligence as a journalist and use the most clickbait title possible for profit.
I’m sorry, but his shit always reads like an AI wrote more than half of it, and when he won’t even ask the people involved like he’s supposed to as a journalist, he’s bringing nothing new whatsoever, only speculation and sensationalism.
That’s all there is to it.