Yes, the people who refuse to either upgrade to Win11-compatible hardware or move to an OS compatible with their existing hardware will eventually get left behind. Both in terms of security and compatibility. It's happened many times, from the fall of AGP in favour of PCIE, to every time Intel inroduced a new CPU socket. X11 is the next.
It's more of an "it's still experimental" kind of issue. They're releasing the Wayland session into the wild before it's ready to boost the pace of bug-squashing. X11 remains default, but they allow the people who want to contribute (instead of whine on public forums about missing features) to test the Wayland session on a much greater variety of hardware and OS configurations than could ever be achieved in-house, report bugs, break things, and submit changes.
In my eyes, it's the same deal as conservatives coping with the changing world. There is a version where they just shut up and let the rest of the tech landscape improve while they happily stick to the X they know (X.org or even XLibre).
That's what happens when you use an experimental feature that is actively being developed and receiving improvements over time. Transitioning an X11 stack to Wayland is not as simple as flipping on a build flag.
Keyboard support has been implemented and will arrive in 22.3:
Wayland support
Under the hood, the Cinnamon keyboard handling relied on libgnomekbd and only worked in Xorg.
This meant that Cinnamon under Wayland could only be used with an English (US) layout.
This new support is fully compatible with Wayland for both traditional layouts and IBus input methods.
Put all of the postcodes in a paginated list that displays only 30 entries at a time (60 and 100 per page for premium users), only has next/previous navigation buttons, orders the entries by popularity, and goes back to the first page if you reload the website. Or an infinitely scrolling page that loads each page dynamically, but returns 429 Too Many Requests if the user scrolls too fast.
It looks like GNOME is the only compositor that doesn't support the wlr_layer_shell protocol, which is anything but surprising. Smithay works (Cosmic and Niri), wlroots works, Kwin and Mir work, Aquamarine (Hyprland) is not listed, but I know that it works.
I think you can get some kind of exemption for archival purposes. I know that the Internet Archive has one. But I also know that ultimately Microsoft is responsible for the data hosted on Github, and Microsoft's interest is to not even risk getting sued.
That tells me you don't understand what a "stable" release branch is. The Debian maintainers do a lot of work to ensure that the packages not only work, but work well together. They don't introduce breaking changes during the lifecycle of a major branch. They add feature updates between point releases, and continuously release security updates.
In the real world, that stability is a great value, especially in the server space. You'd be insane to use Arch as a production server, and I'm saying that as an Arch user.
At work, we use PiSignage for a large overhead screen. It's based on Debian and uses a fullscreen Firefox running in the labwc compositor. The developer advertises a management server (cloud or self-hosted) to manage multiple connected devices, but it's completely optional (superfluous in my opinion) and the standalone web UI is perfectly usable.
You can absolutely use it without a reverse proxy. A proxy is just another fancy HTTP client that contacts the server on the original client's behalf and forwards the response back to it, usually wrapped in HTTPS. A man in the middle that you trust.
All you have to do is expose the desired port(s) to all addresses:
yaml
# ...
- ports:
- 8080:8080
...and obviously to set the URL environment variables to localhost or whatever address the server uses.
I used it for a while, and it's a decent solution. Similar to Tailscale's subnet router, but it always uses a relay and doesn't do all the UDP black magic. I think it uses TCP to create the tunnel, which might introduce some network latency compared to Tailscale or bare Wireguard.
Right. I spent the last several hours trying to get a mixed batch of Win10, Win11, and Win10-upgraded-from-8 computers to talk to a printer and had just about enough of this argument. If you want a pissing match of who can be the biggest dick, take it to Twitter.
Locking. The comment section is a perfect summary of why so many people don't want to be associated with Linux users. I should've removed the post outright because it is inflammatory, reactionary, and invites toxicity -- evidenced by the fact that the downvotes on dissenting comments are largely made by the same users. I wonder if a pattern might emerge.
There is a discussion to be had about the topic... but it went to exchanging insults and downvoting out of disagreement.
Yes, the people who refuse to either upgrade to Win11-compatible hardware or move to an OS compatible with their existing hardware will eventually get left behind. Both in terms of security and compatibility. It's happened many times, from the fall of AGP in favour of PCIE, to every time Intel inroduced a new CPU socket. X11 is the next.