this post was submitted on 22 Jun 2023
50 points (100.0% liked)
Technology
37724 readers
650 users here now
A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.
Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.
Subcommunities on Beehaw:
This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
A lot of people saying this is a Chromium fork, but According to their blog, that's not fully the case.
So it uses Window's default web renderer. It just happens that the default renderer for windows is the same as Chromium's renderer. In this way it does mean that it has a lot of the same problems as Chromium forks, but the browser itself isn't a chromium fork. (This is also why the macOS version uses Webkit and not Blink.)
Blink is a fork of Webkit. And Webkit was the original rendering engine of Chrome, before Google replaced it with Blink. So the DuckDuckGo browser belongs to the chromium family.
EDIT: And Safari is a distant cousin of Chromium.
And WebKit is itself a fork of KHTML.
I'd like to see if this makes an impact to the file size of the application since they don't have to bundle all of Blink with the browser.