Re:Now DuckDuckGo is building its own desktop browser
by Sebb767 on Wednesday December 22, 2021 @08:15AM
(#29648865)
> How is choosing Firefox over Chromium going to help in that regard?
Chromium is absolutely dominant in that space, since basically all major browsers except Safari and FF are based on it. Creating your own stack is hardly an option and Safari isn't forkable, so if you don't want to support the near-monopoly of the Chrome browser stack Firefox is the only option.
Now, I do agree that FF made some very questionable decisions recently, but so did Chrome (see Manifest v3) and the way it's going right now, we'll have yet another Internet Exporer-like scenario on our hands soon.
Re:Now DuckDuckGo is building its own desktop browser
by mattkevan on Wednesday December 22, 2021 @08:45AM
(#29649193)
Didn’t Google fork WebKit to make Chrome? If I remember correctly, the first few versions of Chrome were actually fully WebKit.
Re:Now DuckDuckGo is building its own desktop browser
by marcellus23 on Wednesday December 22, 2021 @09:39AM
(#29649912)
Yes, I guess by "Safari isn't forkable" he means the GUI application, but WebKit itself is definitely open-source and has been forked before (and is itself a fork of KHTML).
Re:Now DuckDuckGo is building its own desktop browser
by Sebb767 on Wednesday December 22, 2021 @10:03AM
(#29650224)
Indeed, that's what I meant. You can fork WebKit, but you don't start out with a working browser, like you would when forking Firefox or Chromium.
Re:Now DuckDuckGo is building its own desktop browser
by ekianjo on Wednesday December 22, 2021 @08:39AM
(#29649115)
Internet explorer was proprietary. Bad analogy.
Re:Now DuckDuckGo is building its own desktop browser
by Sebb767 on Wednesday December 22, 2021 @10:06AM
(#29650262)
It's still mostly controlled by a single company. The fact that it's open source makes the situation a tad better, but it's still a lot of power and network effect centered on a single entity.
> I believe multiple parties and players help us build a more open and standards based web.
How is choosing Firefox over Chromium going to help in that regard? And why do you think Chromium is a monolithic browser stack by Google? How is it monolithic? I see plenty of "Chromium parts" forked and used in different environments on their own all the time. Blink, V8 or mixed combinations like CEF ... Also what makes you think it's "controlled by Google"? You say you want more open standards, but funnily enough Mozilla is one of those ignoring most new widely adopted and open standards because of ... well, some developer simply doesn't want Firefox to support it. See the "Web Serial API" for example.