検索

Why do people use Slackware? One thing people often miss is continuity. Slackware isn’t just technically stable , it’s culturally stable. The same person, Patrick Volkerding, has guided it for 30 years with the same philosophy: don’t change things unless there’s a real reason. For many users, that long-term trust matters more than new features. You know what Slackware will be next year — and that’s rare today. #Slackware #Linux #UnixPhilosophy #FOSS
返信 1 · Renote 0
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
返信 0 · Renote 0
A very belated #introduction: My name is Justin, of course. My first computer was an Apple IIe with an 80-column card that I learned BASIC on. These days I’m longtime Linux user ( #Slackware —> #Debian) and as of late have been dabbling in #FreeBSD and wrapping my head around #ZFS. I’ve worked with C++, Python, Perl and JavaScript; currently learning #Golang — but am really passionate about a well-written, POSIX-compatible Bourne shell script.
返信 0 · Renote 0