🌗 GNOME 50 劃下句點：X11 時代終結，Wayland 邁入新紀元
➤ 告別 X11，迎接 Wayland：GNOME 50 帶來桌面顯示技術的重大變革
✤ https://linuxiac.com/gnome-50-ends-the-x11-era-after-decades/
GNOME 50 版本標誌著 X11 顯示伺服器的時代正式結束，GNOME 專案在歷經漫長的演進後，已完全遷移至 Wayland 作為預設的顯示協定。雖然 X11 核心程式碼已從 Mutter 和 GNOME Shell 中移除，但透過 XWayland 相容層，傳統 X11 應用程式仍可在 Wayland 環境下運作。此舉讓 GNOME 團隊能更專注於 Wayland 特有的功能開發，如 HDR、色彩管理和輸入處理等，預計將為使用者帶來更佳的桌面體驗。
+ 標題有點誤導，GNOME 50 並不能結束整個 X11 時代，GNOME 的影響力也不是那麼廣泛，它頂多隻能結束 GNOME 自己對 X11 的支援。
+ Wayland 終於要成為主
#Linux #GNOME #Wayland #X11
x11
Doing a routine expansion of my XCompose file! 𝐒𝐨 𝐦𝐚𝐧𝐲 𝐧𝐞𝐰 𝐜𝐡𝐚𝐫𝐚𝐜𝐭𝐞𝐫𝐬. ( So many new characters.) 
I had an idea, and now I’m wondering… how well could this approach scale…?
#lang_en #input #gnu #linux #lignux #x11 #unicode #ime
I had an idea, and now I’m wondering… how well could this approach scale…?
#lang_en #input #gnu #linux #lignux #x11 #unicode #ime
Edited 1y ago
I spent some time experimenting with pekwm and evilwm on my Slackware system, mostly out of curiosity.
Both are lightweight X11 window managers with very different philosophies:
• evilwm: extreme minimalism, very small codebase, written in C
• pekwm: still lightweight, but feature-rich (menus, grouping/tabs, rules), written in C++
I did a very simple, informal check of memory usage (RSS via ps) in a clean startx session: no compositor, no panel, one terminal. On my setup, both ended up in roughly the same memory range (a few MB).
At that scale, shared X11 libraries dominate anyway, so small differences aren’t very meaningful.
What mattered more to me was the trade-off:
• evilwm requires much more customization to reach basic comfort
• pekwm provides significantly more usability with essentially the same resource footprint
Conclusion (for me): pekwm hits a better balance between minimalism and usability.
evilwm is interesting as a learning exercise, but not worth the extra friction for daily use.
This isn’t a benchmark, just personal experimentation and preference.
#Slackware #X11 #WindowManager #pekwm #evilwm
Both are lightweight X11 window managers with very different philosophies:
• evilwm: extreme minimalism, very small codebase, written in C
• pekwm: still lightweight, but feature-rich (menus, grouping/tabs, rules), written in C++
I did a very simple, informal check of memory usage (RSS via ps) in a clean startx session: no compositor, no panel, one terminal. On my setup, both ended up in roughly the same memory range (a few MB).
At that scale, shared X11 libraries dominate anyway, so small differences aren’t very meaningful.
What mattered more to me was the trade-off:
• evilwm requires much more customization to reach basic comfort
• pekwm provides significantly more usability with essentially the same resource footprint
Conclusion (for me): pekwm hits a better balance between minimalism and usability.
evilwm is interesting as a learning exercise, but not worth the extra friction for daily use.
This isn’t a benchmark, just personal experimentation and preference.
#Slackware #X11 #WindowManager #pekwm #evilwm
I revisited the 2018 LWN series “A look at terminal emulators” and re-read its notes on st.
Back then, the articles tested st 0.6/0.7 (Debian/Fedora) and 0.8.1 upstream, a fair snapshot of the time.
I went through the upstream st git history from 2018 → 2025 and mapped many of the issues discussed (Unicode/wide glyphs, input crashes, paste & tmux integration, redraw/latency, escape sequences) to the actual fixes that landed over the years.
No single “big patch”, just steady maintenance:
wide-glyph correctness, crash-class input fixes, bracketed paste terminfo, latency tuning, and modern escape/color handling.
I wrote a short technical note with links to the relevant commits:
https://4c6e.xyz/code_notes.html
(post: Revisiting ST after the 2018 LWN analysis)
I’ve been using st + tmux daily on Slackware and it’s been solid: minimal, fast, predictable — exactly what I want on X11.
#st #suckless #unix #tmux #x11 #slackware
Back then, the articles tested st 0.6/0.7 (Debian/Fedora) and 0.8.1 upstream, a fair snapshot of the time.
I went through the upstream st git history from 2018 → 2025 and mapped many of the issues discussed (Unicode/wide glyphs, input crashes, paste & tmux integration, redraw/latency, escape sequences) to the actual fixes that landed over the years.
No single “big patch”, just steady maintenance:
wide-glyph correctness, crash-class input fixes, bracketed paste terminfo, latency tuning, and modern escape/color handling.
I wrote a short technical note with links to the relevant commits:
https://4c6e.xyz/code_notes.html
(post: Revisiting ST after the 2018 LWN analysis)
I’ve been using st + tmux daily on Slackware and it’s been solid: minimal, fast, predictable — exactly what I want on X11.
#st #suckless #unix #tmux #x11 #slackware
I built a latency meter with an Arduino and a photo transistor to answer one question: Is click-to-photon latency higher on Wayland than on X11?
And the answer is: Yes, actually.
⏱️ 42 ms on X11, compositing off
⏱️ 56 ms on X11, compositing on
⏱️ 64 ms on Wayland
⏱️ 71 ms on Windows 10
Tested with Plasma 6.3.4 and Firefox 137. I will improve my methods and confirm these numbers. See replies for details.
#Arduino #DIY #Electronics #X11 #Wayland #Linux #KDE #Plasma #Latency #Performance #Gaming
Edited 259d ago
Plwm – An X11 window manager written in Prolog
https://github.com/Seeker04/plwm
#HackerNews #Plwm #X11 #window #manager #Prolog #programming #GitHub #open #source
Wrote a blogpost about simple (I mean with a shell and a text editor) #X11 configuration.
Covered topics:
1) #Trackball configuration for left hand. Also remapping of some buttons to have scrolling and middle button (not exists out of the box).
2) Theming: #GTK2 #GTK3 #QT , installing cursor(s), fonts and icons.
3) #Xrandr for multimonitor configuration
4) #Xserver settings for #HighDPI
5) #XDG utils and #Emacs as a system file manager
6) #XDM login window
https://eugene-andrienko.com/en/it/2025/07/24/x11-configuration-simple.html
Delightful commons news 🔥
Thanks to @nlnet I was able to give new impetus to delightful commons, and yesterday added new sections to the #fediverse experience list:
https://delightful.coding.social/delightful-fediverse-experience
New sections added under Fediversity:
- ActivityPub bots
- Browser extensions
- Fediverse metrics
- Tools and utilities
- Mastodon API based
🥳 Even better.. There is a new delightful list created and maintained by @lmemsm and collecting delightful #X11 resources.
Check it out at: