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.