[deleted]
Orion Browser
111–120 of 142 posts
Re: Orion Browser
#112Earlier quoted context omitted.
Oh I didn't know! I thought it was Chromium under the hood which is just very memory hungry. Is Chromium actually Swift under the hood?
Chromium is C++, i.e. native. The amount of memory used is a separate issue for the most part, and any language or execution environment can use a lot.
Ah okay thank you for the correction. I had heard all this talk about how Electron is based on Chromium which is why developing with it tends to create memory intensive apps or something. Happy to be wrong on that.
Re: Orion Browser
#113I pay for Kagi. I'd also pay for Orion if it were on Linux. It doesn't even need to be good, I'd still pay for it.
Kagi seems really expensive? They say 240 searches a month costs them $3. But I don’t see how that works. You can run a c5.18xlarge instance for a full hour for that price, and it seems unlikely every search takes 15 seconds of CPU time on all 72 cpus.
Of course they may need multiple instances to search in parallel, but the math per user/search would remain the same.
It’s still nice that someone is making paid search though, and that alone would be enough reason to pay :)
Re: Orion Browser
#114I pay for Kagi. I'd also pay for Orion if it were on Linux. It doesn't even need to be good, I'd still pay for it.
Kagi seems really expensive? They say 240 searches a month costs them $3. But I don’t see how that works. You can run a c5.18xlarge instance for a full hour for that price, and it seems unlikely every search takes 15 seconds of CPU time on all 72 cpus. Of course they may need multiple instances to search in parallel, but the math per user/search would remain the same. It’s still nice that someone is making paid searc…
They pay for search APIs. I would say it's very cheap – $10/month for something I use hours a day comes out to a few cents an hour. Even if I was making minimum wage and it only increased my productivity 1% it would be worth it.
Re: Orion Browser
#115Earlier quoted context omitted.
Chromium is C++, i.e. native. The amount of memory used is a separate issue for the most part, and any language or execution environment can use a lot.
Ah okay thank you for the correction. I had heard all this talk about how Electron is based on Chromium which is why developing with it tends to create memory intensive apps or something. Happy to be wrong on that.
Yes, Chromium is native, but apps built with Electron are written in (or compiled to) JavaScript or WebAssembly, so not native, which uses more memory. Since Chromium is a full web browser it has a kind of minimum memory use which is higher than simple Electron apps would take if they were rewritten to be native. But if you're making a browser, you're going to need all that anyway.
Re: Orion Browser
#116Earlier quoted context omitted.
Kagi seems really expensive? They say 240 searches a month costs them $3. But I don’t see how that works. You can run a c5.18xlarge instance for a full hour for that price, and it seems unlikely every search takes 15 seconds of CPU time on all 72 cpus. Of course they may need multiple instances to search in parallel, but the math per user/search would remain the same. It’s still nice that someone is making paid searc…
They pay for search APIs. I would say it's very cheap – $10/month for something I use hours a day comes out to a few cents an hour. Even if I was making minimum wage and it only increased my productivity 1% it would be worth it.
Haha, yeah, for you it’s cheap. I don’t search nearly as much. I’m wondering how the math works for them.
Re: Orion Browser
#117Earlier quoted context omitted.
This hasn’t been shown to be true in any meaningful way.
I think it is if the the extension does it’s thing without any user interaction? At least I remember reading that that was why the Bitwarden extension is so safe. It doesn’t do anything until I press a button.
Indeed - in the past, some browser extensions would auto fill into iframes and similar, using the origin identity of the page container, even when the field was invisible. That's obviously an issue, but sticking to manual actions (partly) helps there.
The downside of not using a password manager is that users enter (or paste) their passwords without any robust domain validation. In phishing scenarios, a missing auto fill prompt is likely to be enough to encourage a pause and think.
Re: Orion Browser
#118FAQ is missing the only thing I care about: will it support any open platforms.
That probably means they won't, which is disappointing.
Although a browser that's not open source is also a non-starter. The main differentiating features are tree-style tabs which is available as an extension to other browsers anyway. And zero-telemetry, except it doesn't run on a zero-telemetry OS, so again if I want zero-telemetry this is essentially useless to me.
Re: Orion Browser
#119I pay for Kagi. I'd also pay for Orion if it were on Linux. It doesn't even need to be good, I'd still pay for it.
What’s the main reason for you to pay for it?
I pay for it to get the benefit of Google's better search results without ads. It's better than DDG, Bing, Google and Brave Search based on my experience... I've had Kagi subscription since October 2022.
Re: Orion Browser
#120Earlier quoted context omitted.
Until MacOS lets you disable OCSP, I don't think a Mac-native browser can be zero-telemetry.
I believe this might work in your HOSTS file: 0.0.0.0 ocsp.apple.com It seems they at least still respect that. Search HN for "ocsp.apple.com" to find a lot more interesting discussion.
This will disable OS updates.
Additionally, macOS talks to the OCSP endpoints of several different CAs, not just Apple.