Earlier quoted context omitted.
No, it's wayland architecture problem. It forces every single DE that will use it to reinvent same thing. There is no good reason to do that, just a lot of duplicated effort. You will not want to have different mouse behaviour when you use different WM. Having it pluggable is fine, even desired, but pushing it on every DE is just waste of effort and just bumps the bar required for any DE to move to wayland. > GNOME i…
That is exactly what libraries are for, not protocols. Should Web Standards mandate the use of a given JS implementation because it hinders the creation of new ones? Also, the million+1 “de” under X are more like skins, there is absolutely no reason for them to exist in that form, they could just build on top of another wayland compositor.
An X11 apologist tries Wayland
281–290 of 453 posts
Re: An X11 apologist tries Wayland
#282Earlier quoted context omitted.
You can also use Gimp via a RDP or VNC session, which will give much better performance on low-bandwidth connections, since those protocols do damage detection, only sending updates of what's changed, and (lossy) compression. I'm not an expert, but my understanding is that the whole X11 is network transparent thing worked great when apps used the X11 drawing primitives. These days a significant number of X11 apps jus…
Is there a user-transparent way to run Gimp over RDP/VNC, similar to "ssh -X" for X11?
You could either use WinApps or create your own script and add it to a desktop entry. Users can then open RDP Gimp like any other application without even noticing.
Re: An X11 apologist tries Wayland
#283I recently tried switching to Linux with a few different distro's (Ubuntu, Elementary OS, etc.) and use Wayland. The thing that sticks out like a sore thumb to me, and which I've been unable to solve, is that apparently it's not possible to configure trackpad scroll speed. At all. From what I was able to gather, Wayland/libinput say they shouldn't be responsible for handling it and instead window managers should[0][1…
Wayland is not GNOME, what you describe is not Wayland problem, but GNOME problem. It's possible in both KDE and Sway. GNOME is probably worst DE imaginable. After 20 years, they still don't have thumbnails in filepicker and even dropped preview side pane in GTK4. I can't even.
I agree. And yet I also still use GNOME. I just really like the GTK aesthetic. And you'll have to pry dash-to-dock from my cold, dead hands.
Re: An X11 apologist tries Wayland
#284Earlier quoted context omitted.
>Is there a single Wayland supporter who finds the user experience to be better than X11? The immediately noticeable improvement with wayland is with respect to screen tearing, especially in multi-monitor rotated configurations. Screen tearing has always been an issue on x11, and while intel/amd drivers do a decent job in basic cases, things that don't work will likely never work given that x11 is mostly deprecated.
I haven't had screen tearing under X.org for more than a decade. Both under NVIDIA and Intel. A nice made-up issue but it's made up.
Re: An X11 apologist tries Wayland
#285How is the multi monitor story? Especially when the resolutions or refresh rates do not match?
If you have neat monitors where the difference in pixel dpi is simply an integer multiple (1×, 2×, etc) it's really good, no issues at all.
If you need fractional diff in pixel dpi (e.g. you want one screen at 1× and the other at 1.5×) it can kind of work, but dodgy - the 1.5× screen will have its windows rendered at 2× then downscaled, so won't be pixel crisp (and the unnecessary 2× render can push limits on old integrated graphics cards)
If you need diff in text dpi, e.g. like setting Xrdb.dpi or gnome's Scaling Factor, then you're up shit creek (but with X11 to keep you company)
Re: An X11 apologist tries Wayland
#286Earlier quoted context omitted.
Wayland is not GNOME, what you describe is not Wayland problem, but GNOME problem. It's possible in both KDE and Sway. GNOME is probably worst DE imaginable. After 20 years, they still don't have thumbnails in filepicker and even dropped preview side pane in GTK4. I can't even.
> GNOME is probably worst DE imaginable I agree. And yet I also still use GNOME. I just really like the GTK aesthetic. And you'll have to pry dash-to-dock from my cold, dead hands.
Re: An X11 apologist tries Wayland
#287Earlier quoted context omitted.
Wayland forwarding has been there for years now: https://gitlab.freedesktop.org/mstoeckl/waypipe Is it seamless enough for what you had in mind?
I think GP was talking about how ssh has the -X and -Y flags for forwarding X, but you need to do something like -L XXXX:localhost:YYYY to ssh forward. TigerVNC (and some others) will do e.g. "-via foo@bar :1" which GP might not know, but is rather convenient. Xpra is still a better replacement for -X when launching a single application though.
My main use case is launching one-off visualization tools on a remote system that I'm ssh'd to anyway. ssh -X is hard to beat in terms of convenience for that use case, and e.g. a persistence setup would be overkill.
Re: An X11 apologist tries Wayland
#288Can someone explain to me why Linux users seem to like arguing about purely technical pieces of their system like the init manager or the compositor as if it significantly affected them? It’s something I have always found strange.
It's not that strange really.
Re: An X11 apologist tries Wayland
#289Wayland seems pretty good to me now. There are still the odd issues with HiDPI but I think that's mainly down to XWayland support in apps that don't support Wayland natively yet. e.g. If I'm running VLC and I move it from a 1:1 screen to a HiDPI screen then my mouse pointer goes tiny as it passes over it. It's a similar situation for some older Electron based apps too. Support for XWayland is OKish but not seamless.…
Mixed DPI is basically unusable on Wayland due to X11 apps but last I checked, X doesn't even support this at all. I gave up waiting because years later still almost every non Gnome app is electron or otherwise running in XWayland. Just changed my monitors to have the same dpi scale.
Xorg/RandR provides the necessary info, but it is up to the apps (really, toolkits) to work with that and to do it properly it needs the cooperation of both window managers and applications(toolkits) to define some messages/events for scaling, etc. It shouldn't be any different than the other common stuff between X clients, like ICCCM and EWMH (if anything, it should be part of a new version of EWMH), but nobody has bothered so far.
Also there is the -separate- issue where under XWayland, Wayland is lying to X about DPI so apps cannot scale themselves if needed. E.g. Lazarus/LCL has its own scaling logic which works even with the Gtk2 backend (Gtk2 has no scaling logic itself) under Xorg but under XWayland the compositor is lying to the program that is running at 96 (or whatever "non-hidpi") DPI and does bitmap scaling instead (so applications appear blurry). Or at least this is how it is under KDE (which is the only DE i have installed on my PC to use as a secondary environment for testing out stuff - i mainly use Window Maker myself as my main environment).
Re: An X11 apologist tries Wayland
#290i agree with a lot of this; > I was not happy so see that my mouse felt laggy i also noticed this immediately and it was infuriating. my display runs at 240hz, so there must be at least 2, maybe even 3 frames of latency for it to be noticeable. it's made more perplexing that wayland was supposed to represent a reduction in latency. > Out of the box, there’s a bit of that in wayland too, but sway has a way out: max_re…
There is also Xenocara, but that is OpenBSD's Xorg almost-fork (they do track updates but also apply their own modifications).