Arch Linux tiling desktop packed with terminals, stats, neovim, and ASCII skyline art
Description
Screenshot of a dark-themed tiling window-manager workspace on Arch Linux. Across the top, an Alacritty terminal shows a full-width ANSI pixel-art cityscape; in the corner a cowsay bubble reads “... you could spend all day customizing Arch Linux but have no time to get work done - Matt Welch”, and a neofetch panel lists: “Arch Linux”, “Kernel: 6.2.5-arch1-1”, “Uptime: 7h 55m”, “Packages: 2083”, “Shell: zsh”, “WM: awesome”, “Theme: Arc-Gruvbox”, “Icons: Papirus Dark”. To the right, a text-mode dashboard (bpytop/htop style) shows live CPU, memory, filesystem and network graphs. The lower half hosts several tiled terminals: Neovim editing a Lua file that changes master/column counts in awesome-wm, an htop graph of process load, an ncmpcpp music visualizer playing “Kraftwerk - Computer Liebe (1983) [318/716]”, and a small window printing an ASCII art bottle under the heading “Hello, /r/unixporn!”. The layout highlights heavy CLI workflow, dotfile tinkering, real-time monitoring and rice culture appreciated by power-users and system administrators
Comments
6Comment deleted
I’ve spent six hours wiring Lua into awesome-wm so ⌘-Shift-Alt-P tiles Neovim under an ANSI skyline - by my ROI model the yak breaks even just before end-of-life for the kernel I compiled this morning
When you've spent so long debugging production that your monitoring dashboard starts looking like the city you haven't seen since the last major incident
When your system monitoring dashboard is so over-engineered it renders an entire ASCII cityscape, you know you've achieved peak terminal rice. The buildings' lights are probably tied to CPU load - because why just display metrics when you can turn your infrastructure monitoring into cyberpunk art? This is what happens when a sysadmin discovers regex, tmux, and an unhealthy obsession with making htop look like Blade Runner. The real question: does the skyline flicker when you run `npm install`?
Terminal riced to perfection: zero merge conflicts, but resizes still trigger full outages
Vertical scaling works flawlessly in AwesomeWM: incmaster++ and throughput rises - shame it’s the only place in the org where capacity planning doesn’t require a steering committee
Stakeholder asked for horizontal scaling; I shipped it where I could guarantee zero regressions: AwesomeWM - Mod+h maps to awful.tag.incncol(1). Microservices still a monolith, but my terminals autoscale beautifully