It would seem that the Brave browser and Firefox share similar goals on privacy. It’s hard to navigate the differences in their perspectives on this, why would one choose one of these browsers over the other if concerned about online tracking?
Firefox’s Fight for the Future of the Web
101–110 of 296 posts
Re: Firefox’s Fight for the Future of the Web
#102The article once more reiterates the fact that Apple doesn't allow other browser engines. You cannot even fight, there is no future ;-) on iOS.
I wonder why no antimonopolist issue was raised there by e.g. EU. Like they did for NFC in Germany - they forced all phones with NFC to be open to use by different apps, which might finally bring other pay solutions to iOS (or non NFC capable iphones to Germany).
Re: Firefox’s Fight for the Future of the Web
#103Earlier quoted context omitted.
Too bad they built Brave on Chromium instead of Firefox. Which of course given that the company is run by Mozilla co-founder Brendan Eich is a bit of a shame. Firefox is showing that they are more than technically competent to keep up with Chromium and deliver great performance and functionality. With the work they are doing rewriting Firefox component by component in Rust, Google will have their work cut out keeping…
> With the work they are doing rewriting Firefox component by component in Rust, Google will have their work cut out keeping up in terms of performance using their C++ implementation. I would expect Blink’s C++ implementation to perform comparably; wouldn’t the main benefits would be security-related?
In theory you could do this in C++ of course but in practice, both Google and Mozilla have struggled with this for many years and both have still some major bottlenecks in their browser rendering pipeline that are effectively still single threaded and can end up blocking the main thread.
This the main reason Rust was invented (by Mozilla) and they've delivered a few component rewrites that leverage e.g. multiple cores. They've been shipping this bit by bit for the last two years (since the quantum release) and they're not done yet. E.g with the latest releases they've started to ship the new web render on some hardware/os combinations.
Faster is a simplistic notion that is hard to quantify but having a more smooth loading page, with less visible stuttering, and higher frame-rates for animation is sort of the main goal here. People also care about memory usage, energy drain on laptops, etc. If you look at all of this then it used to be the case that people went from Firefox to Chrome to improve the experience and you now have people moving the other way.
Re: Firefox’s Fight for the Future of the Web
#104It seems you are either for-profit, and then you have no ethics and do everything you can to centralize the world around you with no concern for users or their benefits. Or you're a not-for-profit foundation or the Internet Archive, where you do good things but are destined to be "poor".
Are there are any "shades" between those two organization models?
Re: Firefox’s Fight for the Future of the Web
#105Earlier quoted context omitted.
I wouldn't suggest an alternative funding model as much as guess what will it be maybe a year or two from now. Key quote from the article: > Mozilla has launched Monitor, a data-breach reporting service; Lockwise, a password manager; and Send, a privacy-focused alternative to services such as WeSendit. It’s also beta-testing a VPN (virtual private network) service, which it hopes to market to privacy-conscious users.…
I guess they can also add a messenger, news client, a calendar, and an address book and call it Firefox Communicator....
Re: Firefox’s Fight for the Future of the Web
#106The article once more reiterates the fact that Apple doesn't allow other browser engines. You cannot even fight, there is no future ;-) on iOS.
If Apple allowed Firefox on iOS - real Firefox with the rendering engine and extensions and everything, just like Android - I probably would have switched already. As it stands, I stay on Android mostly for Firefox.
One reason I haven’t switched from iPhone is that I’m not confident in my ability to secure an Android, and I’d rather trust Apple than Google.
Re: Firefox’s Fight for the Future of the Web
#107Firefox’s Fight for the Future of the Web, severely cramped by their complete economic dependency on Google and their inability to allocate their funds intelligently
Something like 75% or more of their revenue comes from AdWords - ads run against search. This is one of the most attractive streams for advertisers ever built. You have a prospect ready to buy (often) who is literally telling you in written software processable words what they want.
AdWords dwarfs all of Facebook in revenue, for context. It is the very foundation of Google. In a way, everything else they do is either support for AdWords or a side project.
The money they give to Firefox is not charity. It is to feed this cash cow. They have a similar arrangement with Apple for iPhone default search engine in mobile Safari. I would argue it is far far more valuable for Google to support Firefox in order to ensure search dominance than to waste that money to advance Chrome. Chrome exists to support AdWords not the other way around.
Re: Firefox’s Fight for the Future of the Web
#108Earlier quoted context omitted.
Too bad they built Brave on Chromium instead of Firefox. Which of course given that the company is run by Mozilla co-founder Brendan Eich is a bit of a shame. Firefox is showing that they are more than technically competent to keep up with Chromium and deliver great performance and functionality. With the work they are doing rewriting Firefox component by component in Rust, Google will have their work cut out keeping…
> With the work they are doing rewriting Firefox component by component in Rust, Google will have their work cut out keeping up in terms of performance using their C++ implementation. I would expect Blink’s C++ implementation to perform comparably; wouldn’t the main benefits would be security-related?
But no, I do disagree. Rust is more expressive than C++ and much easier to debug. I expect the new Gecko development to be easier and faster than Chromium, what leads to more features.
Re: Firefox’s Fight for the Future of the Web
#109I see a problem, though I have no alternative to offer, with the current model of organizations. It seems you are either for-profit, and then you have no ethics and do everything you can to centralize the world around you with no concern for users or their benefits. Or you're a not-for-profit foundation or the Internet Archive, where you do good things but are destined to be "poor". Are there are any "shades" between…
Re: Firefox’s Fight for the Future of the Web
#110Earlier quoted context omitted.
One cannot have writeable executable memory on iOS (apple can, we cannot). Thus one cannot make a JIT compiler for js and thus pages are slow. Game engines such as Unity use il2cpp to go from the C# stuff into C++ that can be statically compiled as running the C# as bytecode would be too slow without a jitter.
> One cannot have writeable executable memory on iOS (apple can, we cannot). Nitpick: you can but you cannot ship it via the App Store.