well first try failed miserably. Missing libraries and things that the apps need ( both 'regular' binary and an appimage.. the last 2 things i care about that has not been ported, happens to be one of each ). Don't feel like looking into how you add libraries to the 'emulation' tonight. Tired. But its interesting enough i will try soon.
2021-09-06 11:35 from Nurb432
Well this is neat. x86 emulation for ARM64. It only will run linux
binaries so its not a 'true' emulator, and uses native ARM
interfaces/libraries to improve speed. ( so i guess sort of like wine
is for windows binaries ) Not sure why i never noticed this before.
Could be beneficial to a lot of people.
It looks useful for running printers with propietary plugins that are only released for x86 :)
So, here I am on my main desktop running the Wayland display server. I suppose it's a good thing that the experience is indistinguishable from X. Everything "just works" -- but I suppose a lot of that has to do with the fact that a rootless Xwayland server is running, so anything that needs X will go through that.
I have been playing around to see what works without X, by doing "unset DISPLAY" and then running various programs from the command line. Most of the system apps seem to be fine. My browser is Brave, which is a Chromium derivative; it wants to run in X by default, but I found that if you do "[browser_name] --enable-features=UseOzonePlatform --ozone-platform=wayland" it will use Wayland instead. According to [ https://tinyurl.com/yhznexse ] the new renderers will be enabled by default in Chromium-derived browsers in the next version, so it'll probably do that by default.
All in all, I think they managed the transition pretty smoothly. Most users are just going to be upgraded to Wayland in some upgrade in the near future and they won't even know the difference.
This could be nostalgia too, but i miss the days when i was running VSTa and MGR. Far simpler times.
Who knows, after i retire i may just turn it all off.
Funny. Decided to reach out to Andy Valencia to see if hes still around. ...he is.. nice to hear from someone from that far back in the past. Sort of like being around here, from the old days. A lot of us are not at this point.
All in all, I think they managed the transition pretty smoothly. Most
users are just going to be upgraded to Wayland in some upgrade in the
near future and they won't even know the difference.
There's still a bit of annoying flicker in certain Java apps that use tooltip-like windows over Xwayland. So the X compatibility is not perfect, yet. Almost but not quite.
Java is not going to be a native Wayland stack any time soon.
Here's a link into the middle of a thread on a possible Java/Wayland port:
They're still at the phase of figuring out which toolkits to use:
"And I think the first phase of the project needs to be an investigation
of the alternatives
and consideration of how well it matches all the requirements.
I would not want to see a "code first, figure it out later" approach.
This is going to be discussed in committee for a year before the project even starts ;)
2021-09-16 22:32 from IGnatius T Foobar
Heh. It looks like there are some people who are part of a "just use
GTK and let them deal with it" camp. That would work, but it would be
nice to go native if they can. Then again, people sure do like their
If you read the whole thread there are some comments about how wayland natively does much less than X did. So implementing "native wayland" doesn't implement all the extra protocols that you need to talk to your desktop environment do window resizing or drag/drop or whatever. That's all GTK.
I'm not enough of an internal expert to know one way or the other, but I can see how if Java were to go with GTK, they might need to submit a fair number of patches to GTK to expose all the lower-level stuff they need.
And that might end up being the middle ground. GTK renders to Wayland by telling Cairo and Pango to draw on EGL surfaces, so perhaps Java could do the same thing.
Or I could be completely wrong -- it's been a long time since I've written a GUI program in Java.