As a happy FF user on Mac, Android and Windows, I'm badly missing FF add-ons for iOS (iPadOS actually) - this is due to Apple's policies on iOS prohibiting apps from downloading plugins outside of the App Store. The web without an ad-blocker and proper cookie cleanup (not to talk about FF containers) is impractical to me right now.
Maybe I (or someone) inspired by custom browser project like the OPs, will someday bundle FF with crucial add-ons for iOS and ship that through Github. It would probably need a dev account to install it in iOS/iPadOS, but it sure would be worth it. What I don't know is if regular FF add-ons (uBlock, cookie autodelete, etc.) will work on iOS FF since it runs with a bundled Safari webkit renderer, another Apple iPhone v1 2008-era-restriction for such delicate piece of hardware (weak battery, mem and cpu) that makes no sense now with powerful 2020 devices.
It's proprietary (and the full version is 9.99 a year IIRC), but I've found 1Blocker[1] to be very good on iOS/iPadOS. Admittedly I'd prefer a proper port of Firefox (with JIT), but I can't see that happening for a few years at least. iPadOS 14 is rumoured to include Xcode, so I'm hopeful that might herald a reduction in Apple's restrictions on third party applications.
> Maybe I (or someone) inspired by custom browser project like the OPs, will someday bundle FF with crucial add-ons for iOS and ship that through Github. It would probably need a dev account to install it in iOS/iPadOS, but it sure would be worth it.
If you're going to distribute it outside of the App Store, then the restrictions on JIT and third party addons wouldn't apply. You could conceivably have a full port of Firefox installed via AltStore (for non-jailbroken devices) or Cydia (for jailbroken ones).
I haven't tried it. But seeing as AdGuard is open source, I'll check it out and compare this week. If AdGuard is any better, then you've just saved me a tenner a year, so thanks.
I bought 1blocker like a week before 1blocker X came out and I’m still mad about it. I guess I should just bite the bullet and pay for the new one, 1blocker legacy has worked pretty well but it’s stopped blocking most ads.
Safari is my daily driver, but I switch to Chrome when doing web development because the development tools were vastly superior (10 years ago I was in love with Firebug, but I don't think it's kept up with Chromium's dev tools).
Same here. Safari day to day and Edge/Firefox for dev tools
Safari ticks all the boxes for me:
- Power consumption
- Minimal UI that is elegant and easy on the eyes
- Font rendering is much nicer (especially when compared to Firefox)
- Enter a word in the search bar and usually Siri will show you the exact website and just select it to go there. Other browsers will take you to search page first then you select the first result to go there
- SMS integration for 2FA
- Bookmarks UI is so much cleaner than any other browser.
Speaking of bookmarks, why the fuck does Edge and Firefox store any bookmarks created on your phone or tablet under a separate top level section "Mobile Bookmarks"? It is just so unnecessary and adds needless UI interaction just to get to it.
Do you use content filtering / ad blocking technology in conjunction with Safari? Last I tried to use Safari, it seemed some of the most common tools could not be plugged in / added on to the browser.
Safari 13 eliminated the previous extension scheme. So there’s no more uBlock Origin and similar blockers (there are content blockers, which work differently from uBlock Origin). Since the ad blocking extensions are lists of content to be blocked that’s given to Safari, one is better off using NextDNS or pi-hole for blocking ads (these will work across all apps too).
Wipr is great. Both iOS and MacOS. Safari + keychain is unbeatable IMO. I tried onePassword and I use Brave for dev (Chrome has too much CPU usage, and firefox for Grid debugging). I run Brave / Safari / Chrome / Vivaldi. I find myself in Safari most outside of Dev (zero inside dev).
>- Enter a word in the search bar and usually Siri will show you the exact website and just select it to go there. Other browsers will take you to search page first then you select the first result to go there
Huh? That's exactly what Firefox's "Awesome Bar" does.
Not really. Say I type in “Ikea” into Safari address bar and I have never visited Ikea.com nor is it in my bookmarks; the first option is “Siri suggestions... Ikea.com”. Either click on it or down+enter to go directly to Ikea.com
With Firefox, with the same starting conditions, there is no way to directly go to ikea.com by just typing in Ikea. If there is no history or bookmark then it will take you to a search for Ikea instead
In Firefox ctrl+enter prepends www. and appends .com to whatever word you’ve typed in the address bar, then loads it. So for www.ikea.com, just type ikea then press ctrl+enter.
That was just a simple example. The safari implementation is better, I type in “price” and it expands that to “Priceline.com”; just press enter to go directly there, otherwise either keep typing to narrow or down arrow and enter to search
I use Duckduckgo for search and when I enter anything in the address bar and append !, then I am automatically redirected to the first result of the search. Works perfectly in Firefox.
Current user of Safari as well because of minimal UI and WebKit.
If you are using macOS, Webkit is the most obvious choice because of superior rendering performance, memory usage and energy usage. Chrome/Blink and Firefox/Gecko are not even close (and probably will never be as WebKit is as 'native' on macOS as it can get).
But lack of openness and advanced browser features on Apple's side made me embark on a project to fork WebKit and build WebExtensions API support on top of it (so you can run all Chrome/Firefox extensions on it and get the best of both worlds). We are about half-way through with API coverage. Focusing on macOS first and we have popular extensions like uBlock or Grammarly running already. We also have an iOS prototype running some FF/Chrome extensions.
> build WebExtensions API support on top of it (so you can run all Chrome/Firefox extensions on it and get the best of both worlds). We are about half-way through with API coverage. Focusing on macOS first and we have popular extensions like uBlock or Grammarly running already. We also have an iOS prototype running some FF/Chrome extensions.
This sounds great! Lack of WebExtensions like uBlock Origin and RES were pretty much the reason I switched over to Firefox when Safari 13 dropped, but there is really nothing that comes close to the usability, performance and energy usage of Safari on macOS, so I have been looking for exactly this kind of project for quite some time. I wasn't sure this "compatibility layer" would be feasible to implement, but I guess even supporting uBlock Origin only would make me switch back to Safari in an instant.
Do you guys have a webpage/twitter I can follow or a beta I can sign up for?
Not really. That is just a wrapper, and only supports apis supported by Safari. We are building a new browser with native WebExtension API support on top of Webkit.
Was Firebug still useful in the last years of its existence? It seems to me the dev tools have replaced all functionality. At least that's the reason why I uninstalled Firebug.
I don't remember specifically what they were anymore, but I do remember back when that happened there were still 2-3 features in Firebug not in the official tools that I used regularly. I think one was around ajax requests, the other around CSS. I ended up holding off on the Quantum upgrade for about a year for them.
There is also Firefox developer edition. Its dev tools are a bit more comprehensive than those of vanilla Firefox. I wonder how it compares to Firebug's feature set.
> The decision was made that the next version of Firebug (codenamed Firebug.next) would build on top of Firefox DevTools, and Firebug would be merged into the built-in tools.
> And perhaps most importantly, we joined forces to build the best developer tools together, rather than compete with each other. Many of Firebug’s core developers are on the DevTools team, including Jan ‘Honza’ Odvarko and Mike Ratcliffe. Other Firebug Working Group members like Sebastian Zartner and Florent Fayolle are also active DevTools contributors.
> A huge thank you to them for bringing their expertise in browser developer tooling to the project!
I too use Safari and switch to Vivaldi and Firefox for webdev. I think FFs dev tools have mostly caught on (especially anything CSS related is better in FF) with Chromium, but it's still a bit behind for JS debugging
It also only supports one OS since like 2012 (at least in the past I could run the Windows release in Wine), which may seem like a weird complaint, but it sucks when I need to make sure our web page renders okay for the one business guy who uses Safari and I code on Arch. Thank God for Browserstack I guess.
Epiphany is what they call Safari on Linux: https://webkit.org/downloads :-). It's slow but works well for testing and debugging Safari-specific issues.
Both being built on WebKit is different from both being the same browser, and even before the Blink split, behavior observed in Safari could differ from behavior observed in Chrome. Using observations of Epiphany as a proxy for Safari is just not reliable. I've seen differences between Epiphany and Safari without even trying—where it wasn't a matter of one being too outdated compared to the other.
A lot of things don't work on Firefox, or work worse.
If you are against Google pushing their "evil" stuff on people -- not just you, but all people -- well, Google thinks they can get away with that because people consider their browser better (or those people are just more comfortable with Chrome). Stuff like this, i.e. more options for people, is actually very helpful in reigning Google in a bit. Other Chromium based browsers such as Edge or Brave help as well.
BTW, my personal pet peeve with Firefox is lack of MIDI support, but there are lots of other things. I like that I can search Google by voice in Chrome, and my 6 year old loves that especially. (I don't know if ungoogled-chromium can do that though) I like the way you can grab tabs and drag them around and you know where they will go with Chrome before you drop them. (I have several monitors so this is a many-times-a-day thing for me and it feels awful in Firefox, comparatively). And I hate the ads and recommended sites on the "new tab" page.
This is precisely why I use non-Chromium browsers as my daily driver. It's their constant push for non-standard APIs and aggression towards other browsers that doesn't implement their favored APIs that's cementing their dominance. Not having support for Google features shouldn't be a reason not to support other browser engines.
> I like that I can search Google by voice in Chrome,
Chrome is a blessing for enthusiastic Google users, but not all people feel the same way.
> MIDI support
More access to HW is the last thing I want from the web at this moment. I'd rather that browser vendors focus on making the privacy footprint smaller, not bigger.
> And I hate the ads and recommended sites
You're going to see more of those on Chrome when uBo ceases to stop working along with all other manifest V2 extensions.
> More access to HW is the last thing I want from the web at this moment
This is a big deal, and an irreconcilable philosophical divide. On the one hand web apps need to be able to compete with mobile. They should have access to gyros and cameras and location and offline and push - everything. Mobile apps are modern day Flash and we should strive to be rid of them in favor of a non-proprietary shared platform.
On the other hand the majority of useful information in the world is in document format. We need some sort of non-print-focused (pdf) format that we can use to share documents. Delivering basic documents through what are basically user-land operating systems (browsers) is overkill in every sense of the word: performance, security, accessibility, efficiency, etc.
What to do? The web is already on its march towards being an app platform. The next steps will be tough since Apple and Google also own the much more valuable mobile app ecosystems, and will try to protect them - but it's too late for the web now, the march is on. I think eventually there may need to be some sort of fork of the web to better satisfy both needs.
I'm not sure what you mean by this. It's hard to take Google's push for these sorts of APIs as a push for a "democratic shared platform," let alone see how all this would harm Google in any way.
"Democratic" may not have been the best term to use (edited the original comment), even though, as far as platforms go, the web probably is one of the more democratic ones. I was more aiming for "non-proprietary", "cross-platform" and "shared". Mobile apps are closed ecosystems.
> how all this would harm Google in any way
Owning half the mobile app ecosystem is more valuable than sharing a web.
>> I like that I can search Google by voice in Chrome,
>Chrome is a blessing for enthusiastic Google users, but not all people feel the same way.
My six year old isn't so much an enthusiastic Google user, but she sure does like voice search, since it is really the only option.
>> MIDI support
>More access to HW is the last thing I want from the web at this moment. I'd rather that browser vendors focus on making the privacy footprint
smaller, not bigger.
I'm not really seeing Chrome suffering from privacy problems coming from MIDI devices.
But, you know, if you aren't into making music or learning keyboard or what have you, I guess you wouldn't care about MIDI. It's kind of a big deal to me (and again, 6 year old), so I'd miss it badly. Likewise, if you aren't into videochatting you'd probably be fine if your browser doesn't talk to your webcam or microphone. Etc. Ok.
BTW, if the browser doesn't support MIDI, and you want to use MIDI, you need to install native apps. Those are often a bigger threat, need to be made for each platform, etc.
> if you aren't into making music or learning keyboard or what have you, I guess you wouldn't care about MIDI
Considering the aforementioned problems, why would it make sense for browsers to prioritize MIDI above all else? And I highly doubt your six year old would refuse to use native apps, given the chance.
> (native apps) are often a bigger threat
I choose my native apps with care. For many apps, moving to the web doesn't mean that I would have to stop caring about trust. It just means that I would have to start being more careful about which sites I visit if browsers keep on exposing random HW details.
> need to be made for each platform
If you're only supporting Chrome, then you've stopped caring about portability. You're making it the user's fault if they don't use Chrome.
"why would it make sense for browsers to prioritize MIDI above all else?"
Who said above all else? That's pretty black and white. You could make the same argument if Firefox didn't support, say, microphone or camera. If you don't happen to use them (say, you don't use video chat as many didn't prior to 2020), you could ask why they are so important.
It's just one thing that Chromium does (and has done for year), that Firefox doesn't.
>And I highly doubt your six year old would refuse to use native apps, given the chance.
Which native app? The one she uses only works in a browser, and wouldn't work natively because it uses other things a native app can't use (such as YouTube interaction/synchronization). Also the graphics are far superior to anything I've seen not done in a browser, because it taps into other things that would be immensely difficult if the browser didn't make them available at a pretty high level.
I use my browser to read, watch, and listen, as do many others. I have never heard of people creating music with Chrome. Support for MIDI should be the last thing browser vendors should be concerned with right now.
You probably hadn't heard of people watching videos in a browser until someone made a compelling app. Same goes for so many other things that run in browsers.
The question you haven't answered is why would I want to use a browser for that? Why do you suggest that native apps are unfit for creative purposes? Browsers are somewhat unique in that it's a runtime that runs untrusted code from the internet, and I simply don't want such a security-critical runtime acquiring more capabilities without second thought. Especially for things like access to HW. Remember the fiasco with the Battery Status APIs? Remember how it's main usage in the wild was to enable user tracking?
I agree with you. "Politics" aside, Chromium-based browsers just work better. It's odd that the 10xer super-hacker influencers here think that if you use MIDI, you're part of the problem.
Yes but it doesn't work the same, you don't know what it is going to do until it does it. Try it on Chrome. It's a way more polished UI that gives you a dynamic preview. Makes a big difference especially on multiple monitors.
As for the other things (MIDI etc), is there any confusion?
As far as midi goes, that seems like a feature that is not implemented which is different from not working. That's like saying PDF isn't working in Chrome...
I’ve used Firefox as my daily driver for over 5 years. I’ve literally never encountered what you’ve described. The only reason I use chrome is to cast video to my Chrome cast
So I guess you don't use MIDI. I do. (I develop for it too... you simply can't do stuff like this in Firefox, but you can in Chrome, and it's pretty cool: https://www.youtube.com/watch?v=NV6rdmdZnkA )
And I'm sure you've dragged tabs around, maybe you don't care about the different experience, but it's hard to deny you've seen it.
People want better browsing experience from their browsers, not a terrific MIDI experience. If you want those, native apps would be a better choice from a technical standpoint.
Why are they better? I'm developing for browsers, and it runs amazingly well. I wouldn't know how to build such a thing natively (for one thing, it layers on top of and syncs with music videos), and wouldn't have bothered.
There are tons of web apps, games, etc that "people want." Maybe you don't want them, but other people do. Even HackerNews is more than browsing, since you can post to it.
I get that some people want their browser to do a very limited subset of the things that a browser like Chrome can do. I don't think that is actually the view of Mozilla, but if it was, and they actually advertised that, I suspect they'd have even lower usership.
So I should develop my creative app as a native app because it needs hardware access and browsers don't support that. And browsers shouldn't need to support hardware access because app developers should just build native apps.
Maybe you should try my app. (try it at https://pianop.ly/grid.html ... it works ok in Firefox in "player piano" mode)
All the other stuff other than MIDI, browsers support just fine. (including one critical thing, ability to embed, synch with and overlay on top of youtube videos)
Browsers support an awful lot of things, because people want that. I can tell you with regard to my app, I highly doubt a single developer could build it as a native app that was available to as many people.
Thanks. Yeah I know, I tried to have the fewest words possible. Technically it runs in firefox, you just can't do the midi thing. (my daughter hates watching music videos if they don't have the colored notes displayed and making sounds)
I also suggest that pink is a color of the rainbow, which is an even worse offense from my point of view. :)
I agree. They also have bad defaults (on a fresh install) under the "Firefox Data Collection and Use" section. All of that should be unchecked by default, users should have to opt-in - perhaps with a confirmation - to all data collection.
Firefox is pretty good. The only things I miss are small UI things like muting a website rather than a tab, spell checking, and being able to control the privacy settings for a site directly from a tab rather than having to go into settings and inserting a rule by typing the domain.
Also video playback can be less smooth occasionally.
Firefox has spell checking [0] built-in. Granted, if you want to use several languages it's possible, but clunky - you have to change it every time.
There is also the Language Tool extension [1]. I've discovered this recently and I'm really impressed. I don't use the online service, I run my own server with French and English n-grams and the experience is very good. It auto-detects the language and integrates well in the UI.
There is a tool for merging dictionaries (these are aspell dictionaries internally, iirc), and a number of ready-made merged dictionaries, like English + German, English + Russian, etc. I can attest they work well, without the need to switch.
I wish transparent multi-language support was built in, though.
I am litterally typing "happy Birtdhay to my sister!" on an english version of firefox and see no red underlining ("check your spelling as you type" is checked in the settings).
The feature must be broken or blocked by adblockers I presume.
Zooming on MacOS in Firefox is awful - or least was a few months back when I last checked. It doesn’t smoothly zoom but just bumps font size - complete deal breaker for me.
I keep a copy of Chromium around to test stuff I develop or for the occasional website that doesn't work in Firefox. Ungoogled chromium importance will increase with the continued decline of Firefox's absolute and relative market shares.
Had to check because I thought if anything Firefox's market share had been increasing the past couple of years, but you're absolutely right. I wonder why Firefox isn't performing better in the browser market - it's arguably better than it's ever been.
1. Extensions - almost anyone have some kind of extension installed, and Chrome absolutely wins in that category. that prevents people from switching over to Firefox. Personally I know people that switched to Firefox only after I showed them the extensions they us or an alternative exists on Firefox.
2. Advertisement - Google have a lot more advertising resources than Mozilla. For example, every new Android phone with Google Play Services ships with Google products already installed including Chrome (sometimes as the only browser).
It's not unfounded to think that most people will use the same browser they're using in their smartphone.
> Extensions - almost anyone have some kind of extension installed, and Chrome absolutely wins in that category
I have a bunch of extensions installed on Firefox and don’t use Chrome. What are the Chrome-only extensions I’m missing that means Chrome “absolutely wins”?
This is where Google will shoot itself in the foot trying to kill ad blockers and 3rd party extensions like paywall removers. Firefox is more than good enough, and if you take away uBlock and others that have a loyal following users are going to bail.
The fact that I can run extensions on Firefox for Android is a huge enough win that it's my default system browser.
Keeping in mind that different users have different priorities, I still don't understand why Firefox doesn't make market this as their number one distinguishing feature.
Google amplifies these security conferences where Chrome comes out as a more secure browser than the rest, this leads a lot of corporate IT to enforce Chrome as the default browser on work PC. Some people completely switched their home browser to Chrome just because they like to use one browser at home and work!
The state of translation extensions in Firefox is catastrophic. The useful ones got deleted from the store. As far as I can tell the only reason was to flex some policy choices by the extension store(?) team.
So you pretty much have to have Chromium as a backup if you ever need to research non-Anglo content.
I can see people moving to Chromium because of this and other similar problems with extensions being broken (like the tridactyl thing).
You can use userscripts (e.g. with Violentmonkey [1]) for Google Translate, e.g. [2].
Since you mentioned Tridactyl you might be interested to know that I wrote my own command to inject Google Translate on demand [3].
The extensions you mentioned were removed because they execute remote code. Mozilla are trying to tighten these restrictions [4]. I think Chrome is moving in a similar direction. I don't think that will affect the user script work-around as they execute in the page context, but I could be wrong.
Violentmonkey is very actively developed [1]. Greasemonkey isn't [2]. Tampermonkey is closed source so I view it with some suspicion. Otherwise they're all pretty much the same, as far as I know (I don't use them extensively).
X11 is an old display protocol predating modern concepts of application sandboxing. It gives gives windows lots of control, like allowing them to move the mouse, enter keystrokes, etc. Basically, anyone who has an X11 handle has the same level of access as the user. In Firefox, the process that's supposed to be sanboxed (the content process) has precisely such a handle.
You should use stock Chrome for user testing to get as close to user environments as possible. Little things like a missing http -> https redirect on a subdomain won't be caught in Ungoogled Chromium or Brave.
If I made my money from web development, I would. But it's not my main occupation and I mainly do smaller things as a hobby. There I think it's okay to do this basic kind of testing.
Maybe you don't care about open source browser engine monopoly as much as ubiquitous monitoring?
Without this project, there wouldn't be a way to really make use of the fact that chromium is open source. It frees the world's best browser engine, which IMO is awesome.
Now that I think about it, I bet Chrome has way less or a monopoly than Google's general reach in tracking. Strictly less I suppose since it contributes.
That's hardly fighting Chrome's dominance. The people who Google hired to write Chrome came from Mozilla. Also Mozilla pays its own developers with money that comes from a deal with Google. The online advertising industry, Google's customer base, is supporting and indirectly controlling both of these browsers. Those "evil" things that Googles does are done to offer services to that customer base. Whatever "fight" you might imagine between browsers is, with respect to end users, illusory. Neither browser can pull the plug on the online ad business, they both depend on it. That is the source of the "evil".
I don't agree. While mozilla is taking money from Google, their products don't have tracking built in to them the way that Google products do. They make users aware of the choices they are making and the implications of them. They make plenty of functions available that protect users online from Google, Facebook and other bad actors in this area.
The fight is not illusory, and while Firefox may depend on advertising for financial reasons (although I'm not sure how much it currently is), it is not fundamental to its existence. If someone came along and replaced that money, they would leave it behind. Google on the other hand, is built solely on its ability to gather information about its users and exploit that as much as possible. The two are not the equivalent that your argument claims.
Yes, their products do. Run FF through mitmproxy and look at all of Mozilla's privacy policies and tell me they're not collecting far more data than they should be, at least by default cause 90℅ of users aren't gonna disable most of it. I'm solidly convinced Mozilla is just Google's astroturf.
Google’s Safebrowsing feature alone (that is used in Firefox, too) is a privacy nightmare. They literally have all cookies and all user secrets of all websites that seem “untrustworthy”, which is basically all domains that are not cert pinned in chromium or firefox.
I know this because I initially wanted to implement safebrowsing support for my own browser stealth, but decided against it.
Also, the google PREF (due to safebrowsing background service) cookie isn’t deleteable without physically removing the firefox profile or at least the sqlite databases, just as a hint on whether you are trackable or not.
> The fight is not illusory, and while Firefox may depend on advertising for financial reasons (although I'm not sure how much it currently is), it is not fundamental to its existence
95% of Mozilla's 2018 revenue were generated by Royalties [0], of which 91% are generated by search engine providers. That's a whopping $391 million USD - it will be pretty difficult to fill this gap if Google pulls the plug.
It might be difficult but how is that in any way relevant?
Mozilla's behavior is consistent. Except for a few mistakes that were in my opinion minor, they proved trustworthy repeatedly.
Also let's get the facts straight... all major browsers today are financed from ads, all of them, including Edge, including Safari, including Brave discussed here, all of them.
The ones that aren't financed by ads are simply leaching off the work of others. Of course Brave is a leech while generating revenue from ads too.
Factually untrue. Google is paying Apple billions of dollars ($9 billion in 2018, $12 billion in 2019) to remain the default search engine in Safari.
AFAIK Apple is getting more money from Google than Mozilla does :)
You could say that if this deal went south, then Apple would keep funding Safari, however given they receive a ton of money right now, yes Safari is funded by ads and it goes without saying that they won't do anything to jeopardize those billions of dollars they are getting.
There isn't a single browser right now whose development isn't funded by ads.
Some organizational and individual users have paid for features.
The source code is relatively small, compile time is relatively small. Making small, privacy-focused changes is easy if one is comfortable with C.
One does not use a browser like this for financial or other important transactions. It can be used to do recreational, non-commercial web reading, such as news or other sites one finds posted on HN. One uses major ad-funded browsers like Chrome or Safari for internet banking or e-commerce.
I suppose, but by that logic any web browser is funded by ads unless it either:
1) Doesn't set any default search engine
2) Leaves a great deal of money on the table for no reason whatsoever
Option 2 is stupid, so it's no surprise none of the browsers do this.
Option 1 is a bad user experience regardless of finances. When users type stuff into the search bar, they expect results to come up. You could have a search engine ballot on first startup, but a subset of very-non-technical users is going to be confused by the dialog; there's no good reason to not set a default.
Option 2 isn't stupid, because once you take that money you are beholden to a contract, which comes with both explicit and implicit clauses.
For example Apple would never implement ad blocking by default in Google's Search, not as long as they keep getting payed with _billions of dollars_.
And would Apple even bother to keep improving Safari if they weren't earning so much money from it? Given what happened to IExplorer back in the day, when Microsoft dropped the ball on its development after version 5, I'm not so sure.
Also Safari's content blockers are really easy to circumvent by anti-ad-blocking tech. Doesn't hold a candle to uBlock Origin, which isn't possible to implement on top of Safari. And the available content blockers are so bad many people don't even bother. Fact is Safari is a favorite for ads companies and publishers.
Yes, all browsers are funded by ads, that was the point.
"If someone came along and replaced that money, they would leave it behind."
Who could "replace that money" and why has this not happened?
Mozilla is a bit like Facebook/Google. Users are not paying for Firefox. Advertisers are paying (via Google). It is a service to advertisers. Users need only be enticed to keep using. Data is collected. The primary value of the data is not to usere but to the organisation that collects it and their customers. Mozilla sends data to Google (search queries) and gets paid for it.
tl;dr - Firefox has some telemtry installed by default, including to GA. They have a deal with Google that allegedly prevents Google from seeing the data being collected.
Even so, their products don't do tracking the way Chrome does (which sends a unique identifier per device [0], which can be identified with the user and tracks you on all sites, and which does even more stuff when a site has GA).
I think comparing the two is ridiculous, and is more an excuse to justify using spyware as your daily driver.
[0] There is a unique ID on install, which is allegedly deleted by the browser, but may be stored in the updater. There is a "semi unique" ID set in its place which has high enough entropy (together with the location etc) to be a used as a unique ID. Aside for lots of other phoning home, logging you in to Google, etc.
They are very different, it's been seven years of heavy development since forking. For comparison that's longer than the time between apple forking kHTML to make webkit and the the first release of chrome.
The question was "How different are Blink and WebKit these days?" and "But perhaps that has changed?".
My answer was "they are different" and implicitly "yes", partially because of the heavy development work that has been done since the fork seven years ago.
If you look at the featuresets and when they introduce features I think it's reasonable to conclude they have diverged enough that they can't just pull patches from each other.
Also, there was a webkit mailing thread back when they introduced their cut-down version of service-worker that said that most of the code from blink was basically unusable for them because of the differences.
That’s just a thing that some people say... but it’s actually not true. There is only one of many things in technology and everybody gets along just fine in those situations.
From a user privacy perspective there is not much difference between FAANG. They are all competing for user data. They all want to collect and store it in their data centers. The "significant differences" that some users might think they see are likely a reaction to the lack of viable alternatives.
There is no FAANG which is not competing for user data. Similarly, there is no major browser that deliberately lacks the feature set necessary to facilitate that data gathering. From a user privacy perspective, the difference between "major browsers", or FAANG, is not as significant as it is portrayed by many commentators.
The major similarities far outweigh the minor differences, and I think Mozilla would agree they are not looking to go in a profoundly different direction than Chrome or other major browser. They seek market share and so they will always match the others' feature set. As other comments in this thread elucidate, all these browsers are funded by advertising. As such, we cannot expect the differences to be significant.
If the majority of users are not concerned with things like telemetry, search box queries forwarded to Google, auto-loading resources, complexity, etc., then that is the user base to which Mozilla will cater. The small minority of users who find the status quo unacceptable are not important to Mozilla. Mozilla has enough cash they could prepare a separate, stripped-down bare bones browser in addition to Firefox for those few users who really take privacy seriously who want zero data collection by default.
They won't. That is why we see a user going through all this effort to "un-Google" Chromium. It would similarly take substantial effort to "un-Mozilla" Firefox. Both Google and Mozilla gather user data by default. They each phone home early and often.
The question is how many users would actually be interested in a radically different browser that, by design, made data collection and serving ads much more difficult. Perhaps that number would grow over time as word spread. We will never know. While this could be an experiment of great interest to some privacy-conscious users it is not an experiment of interest to Mozilla, chasing advert-funded "major browser" market share.
Chrome has better security guarantees, and Firefox is also spyware, transmitting user activity to Mozilla without consent.
You could make an un-Mozilla’d Firefox, but at that point you’re better off running this, because once you remove the spyware, Chrome is actually a better browser.
I love Firefox and I'm really thankful for it, but the power consumption is just too high on Mac. Firefox instantly heats up my laptop even with just a single tab open. I like it better than Chrome, but I just can't take the battery/CPU hit for now.
That's weird. I'm working on a MacBook on FireFox 77 with >50 tabs and it's slightly warm at best. I usually am plugged in when doing something like this so I can't comment on battery drain compared to Chrome
Because Firefox is mainly funded by Google and an organisation reliant upon funding from a giant advertising company won't have my best interests in mind
Mozilla is still precious organization even they received money from Google because they developing original browser engine.
Other "privacy-oriented" browser company mostly just uses Chromium. We should against domination of Chromium.
I asked myself this question a lot of times.
The reason is: memories attached to FF.
I used FF for ca. 7 years until Chrome came out. Every time I install FireFox (to give it a try again) all the bad memories come back using it. The whacky design, The Big Slowdown when you had more than 5 tabs open, the accumulation of dead memory, needing me to restart the damn thing every couple of hours or so. The slow Javascript.
When Chrome came out I was amazed, like, I didn't even know how pleasant a browser experience can be until I tried Chrome. It felt revolutionary.
Now Firefox might have caught up but 7 years with all of these problems are still glued to that red/orange logo.
A project like ungoogled-chrome is a welcomed effort, as I cannot imagine going back to FF permanently. They just missed the train, IMHO.
>The Big Slowdown when you had more than 5 tabs open, the accumulation of dead memory, needing me to restart the damn thing every couple of hours or so. The slow Javascript.
Firefox hasn’t been the same Firefox ever since Mozzila replaced the rendering engine with the new Rust-based Servo (https://servo.org/). It’s fast and amazing and handles memory as well (and on my Mac, better) than Chrome/ium.
I think the GP’s point is that Firefox still uses Gecko and some parts of Servo, which is true. Servo is not a complete engine yet and it’s not fully merged into Firefox yet.
Of course it is irrational. It's fairly well studied that humans make a lot of their decisions out of emotions and rationalize it later.
It doesn't make rational sense to buy a coffee from Starbucks. It doesn't make sense to shout in an argument. The fact that people make purchase decisions based on branding doesn't make sense on a rational level.
It's irrational to disregard the influence of emotions on the decision making progress.
What's weird is that you reflect on your emotions, understand that decisions you made are irrational, and still can't see yourself make a different decision going forward. Why did you reflect in the first place? Are you not interested in making rational decisions?
The question is: is FF the "better" browser over Chrome/-ium?
From a technical perspective: the differences are IMHO negligible. Last time I tried FF I couldn't tell any difference. The reaction time of the brain for visual input is something like 180ms(?) and Chrome and FF are faster than that for locally bound functions.
From a moral perspective: sure, Firefox might be the better choice, although the Mozilla Org has a fair share of controversies.
Usability wise: from my last evaluation: minimal. There are functionalities that I liked in FF more, and others in Chrome. So again: from my personal view negligible.
Then there is what I stated above: the memory of cursing about Firefox because it simply "sucked" and Chrome was the best solution for it, you can argue that without Chrome FF would still suck.
The first time I seriously considered switching was when Chrome announced that they would change their API to make uBlock origin's life harder.
So far, I cannot see a strong reason why I should put effort into switching. I run several businesses and projects, all of them are on Gmail and using other Google Services, I have one profile for each business in Chrome, including Chrome's password manager that is storing locally the passwords for all the accounts. It's a lot of effort to switch to Firefox and as stated above at the time of this writing I don't see why I should bother. I rather put in time to run my projects than switching to a different browser, because a lot of HN people are into rust, anti google or whatever.
Chrome is integrated with a lot of Google Products and this makes my work overall more efficient than whatever the switch to FF would gain me as of now.
That might change in the future, and, of course, YMMV.
Edit:
> Why did you reflect in the first place? Are you not interested in making rational decisions?
Actually, I didn't reflect about it until I read the comment of the original parent. I saw a lot of times the comment about "why not FF" on HN, whenever there was anything submitted about "fixing chrome".
To answer your last question: I also don't always force myself to make rational decisions. I DO get a Starbucks coffee once every couple months, I DO like to buy branded products sometimes even though it's not rational (running shoes for example). I DO engage in arguments online once in a while even though it adds not much to my life. So generally I am interested in rationality but I pick my battles and am ok with it when I just give in to my primal instincts. :-)
