Google spent $26 billion to hide this phone setting from you

L4sBot@lemmy.worldmod to Technology@lemmy.world – 71 points –
washingtonpost.com

Google spent $26 billion to hide this phone setting from you::undefined

36

You are viewing a single comment

My problem with this whole thing is that Chrome's only real competition (meaning it's not based on Chromium) is funded nearly entirely by Google paying to be the default search engine. If you aren't going to allow search engines to pay to be the default then Mozilla needs to find a completely different way to make money.

Given the overly wide scope of web browsers it is impossible for a new competitor to create a new browser correctly or securly. The browser market has one path as far as I can see: Firefox dying and overlord Google being on top until we stop using "the web".

I hope not. Not only do I not want to see Google annihilate Firefox but I also don't want to see the further "appification" of every website. It's ridiculous that I need to install an app to pay for parking when I'm visiting a city and will only use the app once. It's not even Bluetooth enabled so it's not like it can be used offline if you don't have a connection.

The fact that Firefox is open source gives me some hope that the community could take the reins and continue development if Mozilla did run into financial trouble.

There's already some forks of Firefox.

Aren't they realistically more "patches" than forks? They continue to track the Firefox codebase as it updates.

Yeah you could be right, I'm not sure about the specifics, just that there's other versions of it.

LibreWolf for example removes the telemetry but is ultimately still updating to each new Firefox version. In the event of Mozilla going under, some project would need to pick up the maintenance of the actual browser core that the "forks" are pulling updates from.

In the event of Mozilla going under

Far less likely than Microsoft "going under" but sure, let's pretend that's a giant concern for the users.

That is horrible but it need not be. Parking paying apps could be federated: you pick the app you like and can pay anywhere*.

Personally I have never used a parking app because they are proprietary and thankfully I live in country where many still uses coins.

I mean, you could just use Firefox or safari, or anything not chromium really. Yeah Moz will take money from search revenue, but they've proven over and over google doesn't tell them what to do.

Heck, chrome exists because google tried to firce Moz to ship a shitty bookmarks implementation, and Mozilla said no years ago. It's literally just an example of a "I'm going to take my ball and go home" tantrum.

I do use Firefox (Librewolf) but Moz are not in control of web "standards" that most websites will follow.

I believe web browsers ultimately should be abandoned and replaced by users with software dedicated to parts of browser functions (e.g. Gemini sites for plain text, video players for video).

Safari is the browser with the second highest usage share and is not in any way based on chrome. It’s limited to Apple platforms though, so other users can’t switch without buying new devices.

Yeah, telling me I can switch from Linux to MacOS is not exactly a solution.

That said, Apple took money from Google to make Google the default on Safari. While I don't think Apple will crumble without Google's money, $18 billion certainly more than funds the development of Safari.

No, Chrome is based on Safari.

Apple took khtml, which was developed by the KDE project, and created Webkit. Google then forked Webkit and created Chrome with it.

https://en.m.wikipedia.org/wiki/WebKit

WebKit and Blink are extremely far diverged at this point, even though Blink was originally a fork of WebKit. Features like sandboxing and process isolation vary significantly on the backend, and feature support for web pages varies greatly. Ask any web developer if they can rely on new web features in chrome also being present in safari, they can’t.

WebKit and Blink are extremely far diverged at this point, even though Blink was originally a fork of WebKit. Features like sandboxing and process isolation vary significantly on the backend, and feature support for web pages varies greatly. Ask any web developer if they can rely on new web features in chrome also being present in safari, they can’t.