Regarding HiDPI and XWayland, there is work-in-progress PR[1] that so far is being ignored by the Wayland developers.
[1] https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests...
The reviewers have asked for some details about the changes and no response yet, it seems unfair to blame the maintainers here.
But of course that goes against the narrative of "Wayland bad".
Android has a similar, if more centralized feedback loop: AOSP drops, device makers build out customizations on top of it, Google adopts some of these features upstream (whether by building new implementations or merging contributions from vendors), and then those vendors go on to building the next differentiating thing now that they don't have to dedicate those resources to individually maintaining stylus support/multiwindow/notification badges/whatever.
As for Wayland,
https://wiki.openjdk.java.net/display/wakefield/OpenJDK+Proj...
> It is very unlikely that distros will be ready to ship all the pieces we need in the next 12 months. So the "short term" goal may actually need to wait for somewhat longer than that.
https://wiki.openjdk.java.net/display/wakefield/Meeting+Note...
The way you made your remark could be understood as if nothing was being done at all.
Don't get me wrong, the blame is squarely on the Java ecosystem that is too slow to keep up with the progress, Wayland developers did great job. The problem is that we still use some of that Java software, or some of that GTK2 software (GIMP), so it's better to accomodate the needs of that software, even if just temporarily.
If anything the whole GNU/Linux ecosystem is too slow adopting Wayland.
Well, there is a wlroots impl, so I've just added a couple lines to wlroots to invoke this support from an env variable without having to modify the actual compositor :D
https://github.com/unrelentingtech/wlroots/commit/5b8308651c...
but the wlroots impl isn't merged either, so I think there's kind of a mutual dependency here. Either your MR or the wlroots MR should go in first!
Just curious, what are the Wayland developers expected to do? This seems like an Xwayland and compositor implementation issue.
Feel free to improve and/or review it. Maybe it's very important to you. But it may no be very important to other contributors, and said contributors are just volunteers.