You’ve done it a thousand times. You’re on Hacker News. You see a link that looks interesting. So you middle-click the story. Then you middle-click the comments. Now you have two tabs open for one article, and you’re about to spend the next five minutes bouncing between them like a pigeon in a psychology experiment.
Switch. Read three paragraphs. Switch. Scroll the comments. Switch. Where was I? Switch. Who said what? Switch. You’re not reading anymore — you’re just managing tabs.
Friction doesn’t announce itself. It just slowly taxes your attention until you forget there was ever another way.
This is the Two-Tab Tax. And every single one of us has been paying it without complaint, because the alternative — complaining about tab management on a forum built in 2007 — feels absurd.
Then someone got tired of it.
A developer named twalichiewicz built a userscript called HNewhere. It does one thing: when you click a link on Hacker News, it opens the article with the HN discussion in a resizable side panel. One window. Article on the left. Comments on the right. No credentials required. No backend. No startup. No pitch deck. Just a script.
And here’s the part that should make every product team uncomfortable: the comments section lit up with people saying the same thing.
“This shouldn’t be a script. It should be built into the browsers.”
They’re right. And they’re also missing the point.
The most dangerous UX problems are the ones we’ve stopped complaining about — because we’ve internalized them as just how things work.
Think about it. Firefox recently shipped a Split View feature. You can right-click a link and open it side-by-side. That’s progress, sure. But it still requires you to know the feature exists, remember the shortcut, and manually trigger it every single time. The browser team solved the mechanics. They completely missed the intent.
Nobody wants split view. Nobody wants two tabs. What people want is to read an article and its discussion simultaneously, without thinking about it. The userscript gets this right because it was built by someone who actually suffers from the problem — not by a committee optimizing for a metrics dashboard.
This is the pattern nobody talks about. The tools that change how we work aren’t coming from product roadmaps. They’re coming from frustrated individuals who build the thing they needed last Tuesday.
Ad-blockers started this way. Browser extensions started this way. Half the features you now consider essential in your daily tools started as someone’s weekend project because the official channel was too slow, too political, or too indifferent to ship.
When a community builds in a weekend what a platform can’t ship in a decade, the problem isn’t resources. It’s priority.
The HNewhere script also does something clever that most platform features wouldn’t think of: if you land on an article that was previously shared on HN — maybe you followed a link from Twitter, from a newsletter, from a friend — the script detects the existing discussion and drops a button in the corner. One click, and the conversation appears.
That’s not a feature. That’s empathy encoded as software.
It recognizes that the value of an article isn’t just in what was written. It’s in what the community said about it. And it refuses to make you choose between the two.
So here’s the real lesson, and it goes way beyond Hacker News. Every time you find yourself working around a tool — opening extra tabs, copy-pasting between apps, building your own little system of hacks and shortcuts — that’s not you being inefficient. That’s a signal. A signal that the tool you’re using has failed to understand how you actually work.
The question isn’t whether this userscript is good enough. It is. The question is why it took a random person on the internet to solve something that every one of us has been quietly enduring for years.
The best product ideas are already out there, hiding in the workarounds people have stopped complaining about. Stop looking at feature requests. Start looking at habits.
HNewhere is a small script. But it represents something bigger: the idea that the gap between what users need and what platforms deliver is growing, not shrinking — and that the people closing that gap aren’t the ones with the resources. They’re the ones with the frustration.
So the next time you catch yourself middle-clicking twice and sighing, remember: that annoyance you’ve learned to live with? Someone, somewhere, is about to turn it into a script. And it’ll probably be better than whatever the official team eventually ships.
FAQ
Q: Isn't this just a niche tool for Hacker News power users?
A: The script is niche. The pattern isn't. Every time you juggle tabs, copy-paste between apps, or build a personal workaround, you're experiencing the same gap between user need and platform delivery. HNewhere is just the clearest example of someone closing that gap with zero institutional support.
Q: Why didn't browsers or HN just build this themselves?
A: Because institutional product teams optimize for broad metrics, not individual workflow friction. Split View in Firefox solves the mechanical problem of side-by-side windows but misses the intent — users don't want to manage panes, they want context without effort. The userscript wins because its builder was also its user.
Q: Does this mean community tools will always beat official features?
A: Not always, but they'll always come first. The advantage of a userscript is speed and empathy — one person who feels the pain builds the fix. The disadvantage is distribution, trust, and maintenance. The real opportunity is for platforms to watch what the community builds and then absorb the best ideas. Most don't.