You’ve probably seen the headlines: KDE turns 30, and someone just pitched an ‘AI-native desktop.’ It sounds like the perfect birthday gift. Radical personalization! A desktop that builds itself around your every whim. Who wouldn’t want that?
But if you’ve actually tried to use an LLM to write QtQuick or QML, you already know the dirty secret the pitch deck doesn’t mention: LLMs are terrible at it. They hallucinate older APIs, spit out broken syntaxes, and generate total garbage. The same tool promising to democratize desktop tweaking is actively eroding the deep technical knowledge that makes it possible.
We spent 30 years fighting for the freedom to control our own desktops, only to happily surrender it to a chatbot.
Most people frame this as open source vs. AI, or KDE vs. DHH’s Omarchy. But the real risk is much quieter. The threat isn’t that AI fails to build the desktop of your dreams. The threat is that it succeeds just enough to become the new gatekeeper.
Think about it. AI models are trained on stale APIs and yesterday’s code. When you rely on them to generate your UI, you aren’t getting the bleeding edge of QtQuick. You’re getting an average of the past. By letting AI mediate the experience, we are flattening KDE’s incredibly flexible internals into a generic, AI-mediated middle ground that nobody explicitly chose.
When an AI hallucinates a Python script, you get a broken app. When it hallucinates QML, you get a broken ecosystem.
We absolutely need good ideas to counter the Omarchy nonsense and push free software forward. But wrapping a 30-year-old, battle-tested architecture in an AI abstraction layer isn’t a feature—it’s a leash. It gives users the illusion of control while quietly degrading the ecosystem’s technical quality and trust. You aren’t customizing your desktop; you’re just prompting a wrapper that happens to sit on top of it.
Thirty years of desktop freedom feels threatened at the exact moment AI offers to make it easier. It sparks a weird mix of nostalgia and fear. For anyone who cares about open-source software or whether the next generation of users gets real control, this is the opening battle.
If we trade deep, reliable customization for a polished AI wrapper, we lose the soul of the open desktop. We cannot let stale, hallucinated code become the new standard.
True customization isn’t just getting what you asked for; it’s having the power to change what you didn’t know you needed.
FAQ
Q: Isn't AI just making coding easier for everyone?
A: No, it's making mediocre coding easier. For complex, state-driven UI languages like QML, LLMs rely on outdated APIs and produce unreliable garbage. It lowers the floor but destroys the ceiling.
Q: What's the practical implication of an AI-native desktop?
A: You get a desktop that feels personalized but is actually just a generic, AI-mediated wrapper. You lose the ability to deeply trust the underlying system because it's built on hallucinated, stale code.
Q: But isn't this just progress? Who cares about deep QML knowledge if the UI looks good?
A: Because looks fade, but lock-in lasts. If we accept an AI-mediated middle ground, we lose the power to fix the underlying system when the AI gets it wrong. We trade true ownership for a polished rental.