Given that Orion (which I repeatedly attempt to daily drive due to the dearth of browsers meeting my requirements right now on macos) is still full of bugs that hamper usability, and seems to introduce new ones with every update, I don't know why Kagi insists on overextending itself like this. They just started porting their broken browser to Linux, they're creating a maps app, all while they clearly do not have the…
Which bugs do you encounter? Orion works nearly perfectly for me.
- Site blocking with /etc/hosts doesn't work consistently with Orion, it intermittently and inconsistently ignores these rules. (this is sort of niche but it's bizarre for a browser based on WebKit)
- The password manager is busted on certain websites that have a third input box (so a captcha or 2FA code), where it'll fill the password twice
- Kept randomly getting the error "Orion can't open this page: This operation couldn't be completed. Cannot allocate memory" with like 10 windows, ~30 tabs open. Haven't seen it recently but like many Orion bugs it is intermittent and hard to reproduce consistently.
- Switching between Chrome and Orion sometimes (inconsistently) switches me to the last Orion window I had open (often on a different Desktop) rather than the one I clicked on.
- On networks where I can form WebRTC connections in Safari and Chrome, I cannot in Orion.
- This was just fixed but until like yesterday, the highlight color in their PDF viewer for ctrl F was a barely visible 10% opacity highlight that was totally unusable.
- Various other intangible performance bugs that seem to pile up when you haven't restarted in a day or two. It starts out really snappy and tends to get slower the longer you've had it open.
I should note that the pace of developement would be much faster if they would open source the browser, but instead of that they keep starting new, closed source projects that will likely have the same fate. Their Linux Orion port is from scratch, none of their macOS code is reusable.