A lot of people saying this is a Chromium fork, but According to their blog, that’s not fully the case.
What’s under the hood
DuckDuckGo for Windows was built with your privacy, security, and ease of use in mind. It’s not a “fork” of any other browser code; all the code, from tab and bookmark management to our new tab page to our password manager, is written by our own engineers. For web page rendering, the browser uses the underlying operating system rendering API. (In this case, it’s a Windows WebView2 call that utilizes the Blink rendering engine underneath.)
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 contribute from the chromification of the web like the 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.
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 contribute from the chromification of the web like the Chromium forks, but the browser itself isn’t a chromium fork. (This is also why the macOS version uses Webkit and not Blink.)
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.
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.