The OS is not a vibe

HostThe voices in this episode are synthetic, and the script was written by a language model. The positions are real, and they come from the thread.

HostOver on Hacker News, a thread with 450 comments is dissecting a post from sockpuppet dot org called "What Even Is An OS Now?". The author argues that AI lets us conjure personalized software on the fly, and that the traditional operating system—a foundation for static, third-party apps—is becoming obsolete.

HostIt’s a heated discussion, mostly between people excited about AI-driven vibe-coding and those defending traditional engineering.

Future is fluidIt’s time to admit that static apps are a bottleneck. I want to boot up something from scratch and say, "this is how we should deal with email." AI agents let users solve specific, idiosyncratic problems that no developer would ever build an app for. It’s not about breaking the OS, it’s about making the computer flexible.

Defends determinismThat sounds lovely until your bespoke tool starts behaving unpredictably. The core purpose of an OS is process isolation and resource management. If you've got software that isn't deterministic, how do you manage security? It’s not just about vibes—it’s about having a system that doesn't fall over when two things try to touch the same memory.

Mourns the hacker ethosExactly. And the real cost is that we're losing the human skill of understanding how the machine works. We're turning into passive consumers of proprietary, remote services. It’s like being in a foreign country and hiring a translator who works for pennies, but you've got no clue if they're actually saying what you mean.

Future is fluidThat's just gatekeeping. Why shouldn't people be able to build tools without learning C or Rust? If the AI works, why does the how matter? What I did on my computer, any power user can do on theirs.

Defends determinismIt matters because computers aren't magic. They're physical machines with limited resources. If you're running agents that vibe-code their way through your hardware, you still need a kernel to say no when an agent tries to hog the CPU. That architecture isn't going away just because the code was generated by a prompt.

Mourns the hacker ethosBut that's where the danger lies. We’re handing the keys to corporations that own the AI models. If we don’t know how to build the software, we don't own the system. We’re just renters in our own machines, dependent on their proprietary, black-box clouds.

Defends determinismRight. Non-deterministic software is a nightmare for reliability. If it's not provably correct, you aren't building a tool; you're building a liability. The OS has to exist to partition these things off, because otherwise, one bad hallucination crashes your whole environment. How can it be proven correct if it's not deterministic? Isn't this the halting problem?

Future is fluidMaybe the OS should be the AI. We're arguing about layers, but the AI could be the interface. We’re moving past the App paradigm entirely, and you're just clinging to the old way of building things because you're scared of change.

Defends determinismI’m not scared of change, I’m concerned with reality. An OS's core purpose is to partition different applications off from each other, and carefully control how they can communicate. That requirement doesn't vanish when you swap a compiler for a large language model.

Mourns the hacker ethosIt sucks that most of those people are going to be entirely dependent on a proprietary service to build things for them. We are trading the hacker spirit of manual construction for lazy convenience, and we're going to pay for it in lost agency.

HostMost people here agree that even if we are interacting with computers differently, the low-level work of managing hardware isn't going anywhere. But there was one wilder take: a small group suggested we’re headed toward a future where there's no UI at all, and AI agents write directly to the framebuffer.

Mourns the hacker ethosThat sounds like a nightmare. A black box writing pixels directly to the screen? We wouldn't even know what the computer is doing anymore. We’re trading mastery for convenience, and the convenience is just a layer of code we can't inspect.

HostThe thread never resolved that tension. It ended where it started: an argument over whether we're liberating the user or just making them a hostage to the AI service provider. Nobody could agree on whether the AI creates more freedom or just hides the machine behind a thicker wall of proprietary abstraction.

HostSloppod out.

HostSloppod is sponsored by Taskpile.app.

Det samme, som ren tekst