Desktop Linux Keeps Winning the Wrong Battles
Posted4 months agoActive4 months ago
howtogeek.comTechstory
calmmixed
Debate
40/100
LinuxDesktop OSOpen SourceFoss
Key topics
Linux
Desktop OS
Open Source
Foss
The article argues that Desktop Linux is focusing on the wrong areas to gain mainstream adoption, sparking a discussion on the goals and expectations of Linux as a desktop OS.
Snapshot generated from the HN discussion
Discussion Activity
Light discussionFirst comment
28m
Peak period
2
2-4h
Avg / period
1.2
Key moments
- 01Story posted
Aug 23, 2025 at 8:13 AM EDT
4 months ago
Step 01 - 02First comment
Aug 23, 2025 at 8:42 AM EDT
28m after posting
Step 02 - 03Peak activity
2 comments in 2-4h
Hottest window of the conversation
Step 03 - 04Latest activity
Aug 24, 2025 at 1:46 AM EDT
4 months ago
Step 04
Generating AI Summary...
Analyzing up to 500 comments to identify key contributors and discussion patterns
ID: 44995409Type: storyLast synced: 11/18/2025, 12:02:55 AM
Want the full context?
Jump to the original sources
Read the primary article or dive into the live Hacker News thread when you're ready.
The other route is where so much software ends up running in the browser that "desktop" linux becomes an irrelevant concept.
If you want a FOSS desktop OS that can win the "right battles", here's what you do:
1. Come up with a name and a logo. Trademark them. Make a basic set of rules that people have to adhere to if they want to use your logo. Obviously, get a lawyer to look it over to ensure it's ironclad.
2. Fork FreeBSD (or any other open-source-but-not-copyleft-licensed kernel)
3. Pick a GUI layer. GTK, Qt, WxWidgets, doesn't really matter as long as you keep the API stable so programs written in 2028 will run in 2038 (good luck doing that on Linux).
4. Create a driver API interface so someone can write a Realtek Wifi driver once and it'll never need recompiled or updated for a newer kernel. The driver file will work in 2028 and 2038 (of course, excepting the case where there's a new CPU architecture, or a security vulnerability).
5. Stabilize the application-level API as well. That means, probably pick a version of glibc and stick with it forever. Patch vulnerabilities, but maintain backward compatibility as much as possible. Application binaries should work forever.
If your instinctive reaction to these bullet points is to think "who's gonna do all that" then yeah, I agree with you. It's not going to happen.
I am happy that I could read things like these in a centralized website in a world where written media is either dying or behind a paywall. There are personal blogs, but who's keeping track of them?
I remember bookmarking techradar, ghacks and others, and reading it religiously every morning. Both went to shit. Don't know if Martin is on here.