Comment on Mozilla CEO quits, org pivots, but what about Firefox?

<- View Parent
7heo@lemmy.ml ⁨9⁩ ⁨months⁩ ago

AOSP is under the Apache 2.0. Yet, if you ever used a “de-googled” lineageos phone, you probably know that the OS you get is a far cry from the commercially supported versions (extremely bare-bones, lots of missing features, lots of apps that don’t work, etc). It used to work a lot better, but as Google integrated more and more apps in their proprietary offering, the FOSS library is extremely terse: Browser (minimal and not production ready), Camera (think the most basic app there is), Calculator (doesn’t support copy pasting anymore AFAICT, I had to install another one), Calendar (same, extremely bare-bones, doesn’t work as is, it needs other software), Clock (that one works just fine), Contacts (same), Email, Files (basic but useful), Gallery, Messaging, Music (dead simple player), Phone, Recorder and Launcher3 (the “home app”). Anything else and you will need to side-load f-droid.

So much so that commercial implementations such as /e/OS have to use alternative implementations such as microG, and put extensive effort in going around the limitations the hard way (providing their own store, etc). In my experience, they are really buggy, and not a commercially viable alternative to using the Google services.

In the end, I use LineageOS as my daily driver on my phone, I have since 2013, but it isn’t without sacrifices (and it is terrible enough that I decided to eventually migrate away from smartphones entirely: the alternative of using a non FOSS phone doesn’t work for me).

One important fact, as I wrote above, is that prior to android 6 (AFAIR), the AOSP offering was a lot more consequent. Google likely realized it cost them money (in dev time), but more importantly opportunities (people using degoogled phones isn’t exactly in their best commercial interest), so they dropped the support for most apps. For example, the launcher app, launcher3, has been unmaintained in quite a while, and ROM distributors, such as Lineage, provide users with their own.

Besides, Chromium might be licensed under LGPL or whatever, but Blink is clearly licensed under the 3-clause BSD license[^1], which does NOT give any warranty whatsoever with regards to sharing the source of components. Whenever Google decides to keep it proprietary, to relicense it, to stop updating the public repository, they can. No questions asked.

[^1]: I “diffed” that license against the 3-clause BSD, and as you can see with the following command, it is a match (don’t blindly believe me, check the sed command, as you can see, the changes are minimal):

$ _URL_REF="https://spdx.org/licenses/BSD-3-Clause.txt"; _URL_CMP="https://chromium.googlesource.com/chromium/blink/+/refs/heads/main/LICENSE?format=text"; _F1="$(mktemp)"; _F2="$(mktemp)"; curl -SsL "$_URL_REF" | dos2unix | sed 's,(c) <<var;name=copyright;original= <year> <owner>;match=\.+>>,2014 The Chromium Authors,; s,reserved\. ,reserved.\n\nThe Chromium Authors can be found at\nhttp://src.chromium.org/svn/trunk/src/AUTHORS,; s/<<var;name=organizationClause3;original=the copyright holder;match=.+>>/Google Inc./; s/<<var;name=copyrightHolderAsIs;original=\([^;]*\);match=\.+>>/\1/; s/<<var;name=copyrightHolderLiability;original=THE COPYRIGHT HOLDER OR CONTRIBUTORS;match=.+>>/THE COPYRIGHT OWNER OR CONTRIBUTORS/; s/"AS IS"/\n&/; s/FOR A/FOR\nA/; s/\(reproduce the above\) \(copyright notice\)/\1\n\2/; s/\(its\) \(contributors\)/\1\n\2/; s/[1-3]\. /   * /; $s/$/\n/' | fold -s -w 72 | sed 's/ *$//; s,^,// ,; s,^// $,//,; 12d; 17d;' > "$_F1"; curl -SsL "$_URL_CMP" | base64 -d > "$_F2"; diff -s -u "$_F1" "$_F2"; rm "$_F1"; rm "$_F2"
Files /tmp/tmp.MQfi4Ya6P4 and /tmp/tmp.YmU8tsdaB0 are identical
$

source
Sort:hotnewtop