A discussion that started with GNU/Linux vs Linux
expanded into sudo vs doas, X11 vs Wayland, and how
system design choices age over time.
I already had notes on dwm, st, and X11 usage, and
this thread was the motivation to turn them into a
short, standalone document about the trade-offs
around scope, ecosystem complexity, and sustainability.
Original thread:
https://swiss.social/@LukePhilipps/115973122695310819
Document:
https://git.sr.ht/~r1w1s1/code-notes/blob/main/notes/Understanding_Wayland_X11_and_Minimalism.txt
Blog:
https://4c6e.xyz/
#Unix #Linux #BSD #Wayland #X11 #SystemDesign #Minimalism
A discussion that started with GNU/Linux vs Linux
expanded into sudo vs doas, X11 vs Wayland, and how
system design choices age over time.
I already had notes on dwm, st, and X11 usage, and
this thread was the motivation to turn them into a
short, standalone document about the trade-offs
around scope, ecosystem complexity, and sustainability.
Original thread:
https://swiss.social/@LukePhilipps/115973122695310819
Document:
https://git.sr.ht/~r1w1s1/code-notes/blob/main/notes/Understanding_Wayland_X11_and_Minimalism.txt
Blog:
https://4c6e.xyz/
#Unix #Linux #BSD #Wayland #X11 #SystemDesign #Minimalism
𝕏 Several New XOrg Libraries See 2026 Releases - Phoronix
「 While we wait to see what comes of the new XOrg Server Git branch plans and a possible XOrg Server 26.1 release, several XOrg libraries saw new point releases this weekend. These seldom-updated libraries saw new releases to ship various build fixes and other minor improvements 」
💪 X.Org Server May Create A New Selective Git Branch With Hopes Of A New Release This Year - Phoronix
「 A proposal has been laid out for a new X.Org Server "main" Git branch to house their development going forward and cleaning up the development lapses over the past few years. Ultimately the hope is for having a new cleaned-up X.Org Server and XWayland Git branch for shipping new releases in 2026 」
Looks like the maintainers of xlibre packages in the FreeBSD 15.0 did a great work
I was able to switch from Xorg to XLibre with just two commands and without any issue, lol
https://eugene-andrienko.com/it/2026/01/22/freebsd-15-0-xlibre.html
Worth to mention, that any of my tricks described in the previous blogpost (https://eugene-andrienko.com/it/2025/07/24/x11-configuration-simple.html) are working too without any problems.
X11Libre: x11/xlibre on FreeBSD: first impressions
<https://www.reddit.com/r/freebsd/comments/1qgcihy/x11libre_x11xlibre_on_freebsd_first_impressions/>
– inspired by a recent claim that "everything works" (better than X.Org) with X11Libre.
The experience with Oracle VirtualBox, and with QEMU (using Virtual Machine Manager), was quite different.
I tried to be fair. From my first comment:
"x11/xlibre is a very early version – 0.1 – I don't expect things to be smooth."
RE: https://mastodon.bsd.cafe/@grahamperrin/115936315972605814
@evgandr the packages are not in FreeBSD, they are in the ports collection.
With regard to an organisation such as X11Libre, this is probably a very important distinction.
Also, please see my recent first impressions.
⚡ GNOME Mutter 50 Alpha Released With X11 Backend Removed - Phoronix
「 The merge "completely drops the whole X11 back-end" with the Wayland session support proving to be in robust shape especially with its state in GNOME 49. XWayland support remains on GNOME for running X11 apps/games but it's all exclusively about the Wayland session moving forward 」
There’s a lot of misinformation going around claiming #GNOME is removing middle-click paste entirely — that’s not accurate.
GNOME (and #Firefox) developers are proposing changes to disable middle-click paste by default in future releases because it’s considered an old #X11-specific behavior that can be accidentally triggered.
Crucially:
— This proposal is about changing the default setting, not removing the functionality itself.
— The ability to paste with the middle mouse button isn’t being deleted; the default will just be off for new users.
— Users who want middle-click paste should still be able to re-enable it in settings (for example via GNOME Tweaks or a GSettings key).
So the narrative that the feature is gone for good is wrong — it’s simply being turned off by default, not deleted.
https://www.theregister.com/2026/01/07/gnome_middle_click_paste/
I have to say, I think it's great that #Fedora is dropping the #X11 session entirely, but I'm also happy that on my main laptop I'm on a distro that takes it slower. Just yesterday I did a teamviewer session with a friend and teamviewer informed that their #wayland support is experimental and indeed it didn't work. Starting an #X11 session fixed it.
There’s a lot of misinformation going around claiming #GNOME is removing middle-click paste entirely — that’s not accurate.
GNOME (and #Firefox) developers are proposing changes to disable middle-click paste by default in future releases because it’s considered an old #X11-specific behavior that can be accidentally triggered.
Crucially:
— This proposal is about changing the default setting, not removing the functionality itself.
— The ability to paste with the middle mouse button isn’t being deleted; the default will just be off for new users.
— Users who want middle-click paste should still be able to re-enable it in settings (for example via GNOME Tweaks or a GSettings key).
So the narrative that the feature is gone for good is wrong — it’s simply being turned off by default, not deleted.
https://www.theregister.com/2026/01/07/gnome_middle_click_paste/
If you're using #Firefox (yes, I still do - despite their recent AI shenanigans, they are still a much better option for privacy than Chrome IMHO), you can use its local translation model to translate any highlighted text - just add a hotkey for the following command:
firefox "about:translations#src=detect&trg=en&text=$(wl-paste --primary | jq -sRr @uri)"
(if you're still on Xorg, replace wl-paste --primary with xclip -o)
🦾 Phoenix Emerges as a Modern X Server Written From Scratch in Zig // Linuxiac
「 it is not yet another fork of the Xorg codebase and does not reuse its legacy code. Instead, according to devs, Phoenix aims to show that the X11 protocol itself is not inherently obsolete and can be implemented in a simpler, safer, and more modern way 」
https://linuxiac.com/phoenix-emerges-as-a-modern-x-server-written-from-scratch-in-zig/
The Input Stack on Linux – An End-To-End Architecture Overview
https://venam.net/blog/unix/2025/11/27/input_devices_linux.html
Patrick Louis writes: ""Let’s explore and deobfuscate the input stack on #Linux. Our aim is to understand its components and what each does. Input handling can be divided into two parts, separated by a common layer:
#Kernel-level handling: It deals with what happens in the kernel and how events are exposed to user-space
[…]
Exposed layer (middle)
[…]
User-space handling:
[…]
The Widgets, #XServer, #X11 window managers, and #Wayland compositors, which rely on everything else
We’ll try to make sense of all this, one thing at a time, with a logical and coherent approach.""
After nearly three decades of KDE desktop environments running on #X11, the future KDE Plasma 6.8 release (due early 2027) will be Wayland-exclusive.
Read the FAQ below to find out what this means for you and the future of KDE:
https://blogs.kde.org/2025/11/26/going-all-in-on-a-wayland-future/