Hacker News new | ask | show | jobs
by monitron 13 days ago
I'm a devoted Kagi user and really want to use Orion but keep running into perf issues and jank that frustrate me enough to switch back to something else. My most recent attempt was this past week.

You all seem to maintain a very fast pace of development (the changelogs are always chock full of cool stuff) but the problems I am hitting have remained broken for ages. Some examples include:

* The app hangs for 1~2 sec partway through typing a URL/search, when using the back button, or during other navigation

* The 1Password extension fails to fill usernames and passwords most of the time, regardless of which version I install. It works fine in Safari, Chrome, Firefox.

* Your built-in ad blocking triggers anti-ad-blocking measures on many news/blog sites now, resulting in the entire page being blocked.

I don't know your business, but maybe pausing new features and pushing for stability/perf/quality of life for a while (a la macOS Snow Leopard) would make sense.

4 comments

“Your built-in ad blocking triggers anti-ad-blocking measures on many news/blog sites now, resulting in the entire page being blocked.“

This issue persists on other browsers with ad blocking extensions? Including on iOS with FF Focus enabled. Is there a browser+extension combination that does not have this issue

I don't know what uBO on FF is doing, but it seems like ages since I've been blocked for using it. Maybe I've just gotten lucky with the sites I visit.
I think those sites are likely using Ad-Shield anti ad block, which is very agressive
Kagi is the new arch Linux.
Thanks for the honest feedback, and I hear you.

Some context that might explain (though not excuse) the situation: unlike browsers built on Chromium or Firefox/Gecko, Orion was built from scratch on top of WebKit. No fork, no upstream codebase to pull from. That means every feature, every integration, every compatibility shim is ours to build and maintain. Browsers that fork Chromium or Gecko inherit years of battle-tested extension support, rendering fixes, and platform work for free — we don’t.

On top of that, the macOS team is 3 people. About 70% of our engineering time goes to maintenance and keeping up with WebKit/OS updates, ~20% to third-party app compatibility (extensions like 1Password, ad blocking lists, etc.), and what’s left — maybe 10% — goes to community support, discussions, and new features combined. That’s why our changelogs look active but long-standing issues persist: we’re constantly triaging a backlog with thousands of entries and making painful priority calls every single day.

None of this is meant as an excuse. You’re right that stability matters, and the issues you describe are real. But this is the cost of building a genuine alternative to the browser market rather than shipping another Chromium or Gecko wrapper. We think that trade-off is worth it for users who want real engine diversity and full extension support without Google’s or Mozilla’s constraints.

That said, we can’t do it alone — that’s exactly why Orion+ exists. If you believe in what we’re building, subscribing is the most direct way to help us grow the team and get to that “Snow Leopard” moment faster.

We’re sorry for the rough edges. We know they’re there, and we’re working on it.

I really appreciate the reply, and all your work. The difficulty of what you're doing is not lost on me; I was honestly blown away that you all launched a browser project at all. I think it's vitally important that the web not become a monolith in terms of user agents (even if, alas, one single rendering engine takes all the market share) so kudos to you.
Orion+ Lifetime buyer here. I strongly believe in Orion and I genuinely hope you reach that Snow Leopard moment. I also used it for months (and still use it for some always-open spreadsheets), but eventually had to switch to Safari due to the perf and stability issues. Funnily enough, you did prove Safari to be a viable daily driver for me, just not Orion itself yet.