The HTTP client for the RAM apocalypse

Open your Activity Monitor right now. Sort by memory. There's a decent chance an HTTP client — the kind of tool you open to fire off a single GET request — is sitting near the top, quietly holding onto several hundred megabytes it isn't using for anything you asked it to do.

That's not a bug in any one app. It's the tax you pay for shipping a browser inside your app so you don't have to write a UI toolkit. Chromium is an incredible piece of engineering, and it is also, categorically, the wrong tool for a window with a URL bar, a few tabs, and a JSON viewer.

The bet

Nop started from a dumb, stubborn question: what if we just... didn't? What if the request builder, the response viewer, the syntax highlighting, all of it, ran on a real native UI toolkit instead of a bundled browser rendering a web app pretending to be a desktop app?

The honest answer is that it's more work. There's no <div>, no CSS grid, no npm install to get a date picker. Every button, every scrollbar, every animation curve gets built by hand against a real GPU surface. We write our own immediate-mode UI, our own font atlas, our own layout code.

The payoff is that Nop launches the instant you click it, and idles at a footprint you can round to zero. There is no splash screen because there's nothing to warm up — no renderer process, no V8 isolate, no IPC bridge between a UI thread and a JS thread. It's one process, drawing what you see, using what it needs.

What "native" actually buys you

• Instant launch. No Chromium to spin up before your first frame.
• Predictable memory. What you see is what's resident — no background renderer holding tabs you can't see.
• One binary. Self-contained, no runtime to install, no auto-updater downloading a new copy of the browser.

We're not precious about it — Electron is a completely reasonable choice for a lot of software, and it got a generation of good tools shipped faster than they'd have shipped otherwise. But for something you open fifty times a day, for two seconds at a time, the calculus is different. The RAM apocalypse isn't a single villain; it's a thousand well-intentioned apps each deciding their few hundred megabytes is fine, actually.

Nop is our answer: give some of that RAM back. Open mode Chrome tabs instead.