You open a new tab. Your laptop fan screams. Chrome has decided it needs more memory than the Apollo missions used to land on the moon. You stare at a loading spinner and wonder where it all went wrong.
Meanwhile, someone built a web browser that runs in a text terminal. Green phosphor on black. No mouse. No tabs eating 800MB each. And it renders the full modern web — JavaScript, CSS, the whole circus.
The modern web doesn’t need a supercomputer. It just thinks it does.
The project is called Duet Browser, and you can try it right now. No download, no signup. Open a terminal, type ssh krnl.duetbrowser.com, and you’re in. What you’ll see is something that looks like it time-traveled out of a 1990s university library — that BBS aesthetic, those green characters glowing against black — except it’s loading websites from 2024.
The creator didn’t do this for funding. There’s no VC deck. No Series A announcement on LinkedIn. Just raw terminal fun, built because brow.sh — the existing terminal browser — wasn’t raw enough. It was too graphical. Too modern. They wanted the real thing: the old-school terminal days, but running today’s web with all its bells and jingle-jangle whistles.
Here’s where it gets uncomfortable.
If a terminal can render your website, what exactly is all that JavaScript doing?
Think about it. You’ve got browsers consuming gigabytes of RAM to display what is, at its core, text and images. The web has become a delivery mechanism for tracking scripts, autoplaying video, cookie banners, and seventeen layers of frameworks compiling other frameworks. We’ve normalized this. We’ve convinced ourselves that a browser needs to be an operating system inside an operating system.
Duet Browser exposes the lie. It strips everything down to fundamentals — a layout engine that works, content that renders, interactions that function — and dares you to explain why you need anything more.
Now, let’s be honest about what this is and isn’t. Duet Browser isn’t going to replace Chrome. It won’t render your WebGL games or display Instagram stories the way Zuck intended. It’s a provocation as much as a product. But provocation has value.
Every bloated system eventually meets someone who refuses to participate in the bloat. That’s when the cracks show.
The early internet had a texture we’ve lost. BBS systems, green phosphor screens, the raw feeling of connecting to something real through a terminal — there was a directness to it. You weren’t being tracked. You weren’t being served. You were just… there, reading words on a screen, and that was enough.
Duet Browser doesn’t just nostalgia-trip you back to that era. It drags that era forward, kicking and screaming, into the JavaScript-heavy modern web and says: deal with this. The result is something that shouldn’t work but does, and the fact that it works is the most interesting thing about it.
For developers, this is a masterclass in what a layout engine actually needs. For everyone else, it’s a gut-check. When a terminal can handle the web, what are we spending all that RAM on?
The best critique of a bloated system isn’t an argument. It’s a working alternative that fits in a terminal window.
Try it. Type the command. Watch the green text appear. And then go back to your browser with its twenty-seven open tabs and its 4GB of RAM and ask yourself the question this project silently poses: did we build a better web, or just a heavier one?
FAQ
Q: Can a terminal browser actually handle the modern web?
A: Yes, but with caveats. It renders text, layout, and runs JavaScript, but heavy graphical content, WebGL, and complex interactive apps won't look or work the same. It's not a Chrome replacement — it's a proof of concept that most of the web doesn't need what Chrome provides.
Q: Why does this matter if nobody will daily-drive a terminal browser?
A: Because it exposes the gap between what the web requires and what browsers consume. If a minimalist engine can render real websites, the gigabytes of RAM your browser eats are doing a lot of things that aren't 'displaying content' — tracking, ad loading, framework overhead, background processes you never asked for.
Q: Isn't this just nostalgia for a web that was objectively worse?
A: The old web was slower, uglier, and harder to use. But it was also lighter, more direct, and less hostile to your attention. Duet Browser isn't arguing we go back — it's arguing we notice how far forward we've drifted from what matters, and how much baggage we picked up along the way.