Ideas on modernizing the open-source desktop
UX veteran Scott Jenson argued at KDE's Akademy 2026 that the open-source desktop must move past the 20-year-old WIMP model, proposing widescreen-first layouts and better working memory tools.
summary is enough Skimming captures Jenson's core arguments and prototypes on desktop UX stagnation, saving you time unless you want to watch the video demos.
summary
Scott Jenson, a veteran UX designer, argued at the KDE Akademy 2026 conference that the Linux desktop has stagnated by blindly following Windows and Mac paradigms for two decades. He critiqued the stateless nature of direct manipulation and proposed rethinking desktop working memory, widescreen-first layouts, and canvas-style clipboards. While acknowledging user resistance to change, Jenson urged open-source developers to experiment rather than waiting for commercial operating systems to lead. Commenters largely defended their customized workflows while debating potential improvements like enhanced clipboards and semantic filesystems.
key points
- Linux desktop development has largely mirrored commercial systems from Microsoft and Apple, which have recently faltered or shifted focus away from traditional desktop innovation.
- Jenson highlighted the curse of direct manipulation where desktops lack working memory, leading to lost contexts and a reliance on fragmented clipboard managers.
- Prototypes demonstrated at the conference included widescreen-centric layouts, an Obsidian-style visual clipboard canvas, and privacy-preserving episodic memory tracking.
who should read it
Open-source desktop developers, UI/UX designers, and power users interested in the future of Linux desktop environments.
discussion mixed
consensus
Many commenters lean heavily into the don't touch my stuff camp, arguing that their heavily customized tiling window managers and keybindings already provide an efficient, stable workflow.
pushback
Some commenters argue that cross-app data sharing and file management remain fundamentally broken, advocating for deeper changes like semantic filesystems or dissolving apps into the OS.
I think we could get a long way toward Scott's "working memory" ask by just making a smarter Clipboard Manager.
Many people don't use a clipboard manager at all, and even what exists today would be a huge upgrade for anyone accustomed to only a single clipboard "slot" that's instantly overwritten the next time you copy anything. Windows has one built in (though turned off by default), KDE Plasma ships with one, MacOS has third-party ones IIUC (not a Mac myself).
But imagine a clipboard manager that wherever you hit Ctrl+C also simply grabs the title of the active window and a deep link/URI …
It bridges high-level UX critique with a concrete, actionable feature that existing desktop environments could easily implement.
Generated by an LLM from the article and thread. Check the sources before relying on it.