You probably don’t think about browser engines. Why would you? Chrome uses Blink. Safari uses WebKit. Firefox uses Gecko. Three engines, three corporate overlords, and a web that runs exactly the way they want it to.
And that should terrify you.
Because when three entities control the foundational layer of the entire internet, “open web” becomes a marketing term, not a reality. Every standard that gets adopted, every feature that ships, every API that gets deprecated — it all flows through a bottleneck controlled by companies whose primary interest is not your freedom, but their bottom line.
The web doesn’t belong to the people who use it. It belongs to the people who render it.
Enter Gosub. An independent, modular browser engine built from scratch. Not a fork. Not a wrapper. Not another Chromium skin pretending to be a real browser. A ground-up engine that has been in development for over two years by a small, stubborn team that looked at the browser oligopoly and said: no.
When they shared their work, one Hacker News commenter summed up the industry’s attitude in five words: “poc or gtfo.” Proof of concept or get out. Nobody believed a small team could build something real.
So they built the proof of concept.
Rendered web pages are starting to look more and more like, well, web pages. The moving parts are connecting. The engine is breathing.
Now, here’s where most people get it wrong. They look at Gosub and ask the wrong question: “Can it match Chrome?” As if the goal of any new browser engine is to replicate the bloated, decade-accumulated feature set of a Google product. That’s like judging a startup by whether it has the same org chart as IBM.
The point was never to catch up to the giants. The point is to prove the giants left something important behind.
What they left behind is modularity. Blink, WebKit, and Gecko are monolithic beasts. They’ve grown through years of accretion — feature piled on feature, hack layered over hack. Want to swap out the rendering engine? Good luck. Want to use just the networking layer? Forget it. These engines are cathedrals when what we need are Lego bricks.
Gosub is built modular from day one. Each component — parsing, layout, rendering, networking, scripting — is designed to be independent, replaceable, and understandable. You don’t need a PhD in Chrome internals to figure out what’s happening. You can actually read the code and trace the logic.
The best code isn’t the code that does everything. It’s the code you can actually understand.
For developers, this is not abstract. Every time you’ve fought with a browser-specific bug, every time you’ve written a hack to work around an engine quirk, every time you’ve wondered why a feature works in Chrome but breaks in Safari — you’ve felt the cost of an oligopoly that has no incentive to make your life easier.
And for the open-source community, Gosub represents something even bigger: proof that the web’s foundational layer is not beyond the reach of independent effort. That you don’t need a billion-dollar budget and a thousand engineers to challenge the status quo. You need a thesis, a team, and the willingness to be told “poc or gtfo” — and then ship the poc.
Will Gosub dethrone Chrome? No. Not anytime soon, and maybe not ever. That’s not the point. The point is that the web needs alternative thinking at the engine level, not just at the UI level. Every browser that ships today is either Chromium in a costume or a fading giant running on fumes.
A web with only three engines isn’t an open web. It’s a cartel with good PR.
Gosub is a bet that modularity beats monolith. That independence beats dependence. That a small team with a clear thesis can push boundaries that trillion-dollar companies won’t, because their incentives are locked into maintaining what already exists.
The web was never meant to be a company town. It was meant to be a commons. Gosub is one small, stubborn step toward reclaiming it.
And if that doesn’t matter to you, ask yourself: when was the last time a browser engine was built from scratch? Not forked. Not rebranded. Built. The answer should make you uncomfortable.
FAQ
Q: Can a small team actually build a competitive browser engine?
A: Competitive is the wrong word. Gosub isn't trying to match Chrome's feature count — it's proving that a modular, independent engine is viable. The goal isn't parity; it's optionality. The web needs alternatives, not clones.
Q: Why does modularity matter to me as a developer?
A: Because every time you've debugged a browser-specific issue, you've paid the tax of monolithic engines. A modular engine means components you can inspect, swap, and understand. Less black-box debugging, more actual control over your stack.
Q: Isn't this just reinventing the wheel?
A: No — it's questioning whether the wheel needs to be a 10-ton monolith. Blink, WebKit, and Gecko grew through accretion, not design. Gosub starts from a different thesis: that the web's complexity problem is architectural, not just a resource problem. That's a contrarian bet worth making.