101–110 of 142 posts
Last I checked this didn't support HiDPI, a technology invented over 10 years ago.
Okay, but X11 is deprecated. Is there a modern version?
At the risk of threadjacking, I'd still love to have a real conversation about how and why this Wayland thing happened (and is still arguably happening) so badly . Specifically, how -- again, in LINUX-LAND -- a whole bunch of people decided, "nah, we're going to go ahead and break the HELL OUT OF backwards compatibility this time, even though we pretty much never do this."
So only interfaces became limited to what's available at that moment and the limited set of Unix software abstractions. Those abstractions are also made extremely use case specific even though there are opportunities to unifiy them like Android did with Binder, Windows did COM and dotnet.
Of course technical difficulties of designing efficient and long-term surviving interfaces also play a role. There are too many hobbyists in the Linux desktop world and too few professionals who also have to work with hobbyists. Many contributions to Linux desktop happen when people are studying and then they leave. This creates disincentives to design long-term systems because they take too long and they are a slog to design and keep up-to-date.
Earlier quoted context omitted.
There's a few related answers to your question, so I'm going to meander a bit and hope you can follow along. First off, backwards compatibility wasn't actually broken. X11 apps work fine under Xwayland. All the weird bikeshedding that happens in Wayland isn't as important because we have working compatibility bridges and all the old stuff still works. Second, "don't break userspace" is specifically a Linux kernel pol…
I don't think that's the issue with Wayland. X11 has fundamental design flaws, Wayland happened because of it. I believe the question is why Wayland happened so badly . Sure, nVidia shenanigans are contributing to bad fame, but arguably that's not the issue with Wayland. However, Wayland fixes some of X11 design flaws but ignores others - or even introduces new ones. But, for example, HiDPI is a mess in X11 - for (I…
Because Wayland's base protocol was unable to replace X11, virtually nobody adopted it when it was initially released in 2008. The subsequent 16 years have been taken up by a grueling process of contributors from various desktop environments proposing protocol extensions to make Wayland a workable solution for their users. This has resulted in endless bikeshedding and requires compromise between different stakeholders who have fundamentally different viewpoints on what the Linux desktop should even be (GNOME vs everyone else). As an example, the process for allowing a client to position its own windows has been ongoing for over two years, and has led to multiple proposed protocol extensions with hundreds of comments on each.
The transition would have been much smoother if Wayland had the same "mechanism over policy" philosophy as X11 and allowed for software to easily be ported to it, but long-term that could have caused the same issues that the Xorg maintainers were facing when they created Wayland.
Package management sucks, and this is my way to deal with it.
I am running linux machines and I have one headless machine. I need to keep a browser running in that machine and occasionally check on it (see what it's doing, and possibly fix things in the browser). Would Xpra let me do that from a remote machine?
With Xpra you have a headless X session on the remote machine and you "detach" and "attach" to it from the client. So whatever X applications you leave running will be right where you left them.
Are there any security implications of running this over ssh?
I find using a ssh-agent to load password protected SSH keys works best.
If you're only working on Linux, you almost surely want waypipe [0] instead of xpra. If you need support for other platforms, though, xpra is still a pretty good solution. [0] https://gitlab.freedesktop.org/mstoeckl/waypipe
Earlier quoted context omitted.
I don't think that's the issue with Wayland. X11 has fundamental design flaws, Wayland happened because of it. I believe the question is why Wayland happened so badly . Sure, nVidia shenanigans are contributing to bad fame, but arguably that's not the issue with Wayland. However, Wayland fixes some of X11 design flaws but ignores others - or even introduces new ones. But, for example, HiDPI is a mess in X11 - for (I…
Wayland happened so badly compared to e.g. the Systemd transition or the Pipewire transition because it was developed by Xorg developers who had spent years dealing with its complexity and countless regressions caused by bugfixes breaking obscure behavior that clients depended on. As a result, they swung too far in the other direction. They came out with a minimal protocol where all the heavy lifting was done in each…
Both of these were shit shows which only look good now to people who weren't around when they were happening.
The first one to dump this into flutter will probably be onto something
If you're only working on Linux, you almost surely want waypipe [0] instead of xpra. If you need support for other platforms, though, xpra is still a pretty good solution. [0] https://gitlab.freedesktop.org/mstoeckl/waypipe
Uh, only if you want to use Wayland.
Plus, if one wants things like functional screen readers, suitable-for-video-games Vulkan frame pacing [0], and many other things that you'd think would be table stakes for a project that's been running for at least 15 years, one's only choice on Linux is xorg.
[0] The only reason the Steam Deck isn't a disaster is because Valve has been carrying a patch for a "Make frame pacing not garbage" extension that the Wayland people have been refusing to merge in for the past two+ years.