this post was submitted on 05 Dec 2023
0 points (NaN% liked)

Technology

59554 readers
3442 users here now

This is a most excellent place for technology news and articles.


Our Rules


  1. Follow the lemmy.world rules.
  2. Only tech related content.
  3. Be excellent to each another!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, to ask if your bot can be added please contact us.
  9. Check for duplicates before posting, duplicates may be removed

Approved Bots


founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] nyakojiru@lemmy.dbzer0.com 0 points 11 months ago (1 children)

Horrific but strategically inevitable, switch to chromium engine, and do your own privacy related fork . Like all the other browsers.

[–] samuelc@lemmy.world 0 points 11 months ago (1 children)

fork

what if google chrome decided to close the fork by changing the license to something restructive, i mean the fork can goes on for a little while but we are still depending on the resources of a Big $$ corporation....

firefox is the only way for a free web....

[–] jcg@halubilo.social 0 points 11 months ago* (last edited 11 months ago) (1 children)

Then they'd be alienating the open source community that makes a lot of contributions (though much of chromium is still essentially built internally). They also wouldn't be able to lock down the code that's already been released under the more permissive BSD license.

Now, a fork of Chromium is its own beast. Some searching shows that just to build it takes 30 minutes on a decent workstation. It's huge, which makes me think it's the kind of project that could only really be maintained by a large company. Not necessarily a Google sized company, but a large one nonetheless if you seriously want to remove the dependency on Google.

EDIT: turns out it's Chrome that takes that long to build, which includes things not in Chromium like Widevine, licensed codecs, telemetry, sync, that kind of thing.