3 ms·

> Pretty sure Firefox uses Chrome as its toolchain these days. It does not. There is no shared code between Firefox and Chrome. They use completely different

> Pretty sure Firefox uses Chrome as its toolchain these days. It does not. There is no shared code between Firefox and Chrome. They use completely different rendering engines with independent histories (Chrome uses Blink originated from WebKit originated from KHTML, Firefox uses Gecko originated from Netscape originated from Mosaic). The only shared component is that Firefox utilizes public APIs for Google SafeBrowsing. Disclaimer: ex-Mozillian

wyldfire 4y ago
Oh sorry. Chrome is not a toolchain in mostly any sense. Except for its extraordinary flexibility as browsers are in general able to execute code. So I thought it was obviously a joke that one would use a browser to compiler another browser. The "on trusting trust" attack regards using your compiler as a mechanism to infect compiled executables -- including compilers themselves, and their generated code. I didn't mean to suggest that the two browsers shared any code.
mintplant 4y ago
There is actually some code sharing these days, mainly libraries. Mojo for IPC is the one I remember off the top of my head. I think also WebRTC stuff?
- tristor 4y ago
  Yes, in the strictest sense both browsers may rely on public open source libraries, which means they have some shared code, but they do not share any code directly with each other (e.g. Chrome is not a dependency of Firefox, Firefox is not a dependency of Chrome). I see this as not equating to "code sharing" because they both happen to use a library. Ironically for other apps that'd usually be something like OpenSSL, but in the case of Firefox and Chrome they actually have entirely separate TLS codebases as well (NSS for Firefox and BoringSSL for Chrome). For some of these shared open source libraries, either Mozilla or Google is the primary contributor/maintainer, and both organizations usually make contributions. This is true across many things, even libraries in the open source space that are not involved in the browsers themselves but may be in the toolchain (Mozilla has produced robust open source CI/CD tooling, bug trackers, etc over its history).
  - deleted 4y ago
    [deleted]
- fomine3 4y ago
  Similarly ANGLE is made by Google (perhaps Chrome team) and now also used by Firefox
I_AM_A_SMURF 4y ago
I mean... the Firefox build has NodeJS in it now, so in a sense Chromium is in the toolchain :-)

wyldfire 4y ago

Oh sorry. Chrome is not a toolchain in mostly any sense. Except for its extraordinary flexibility as browsers are in general able to execute code. So I thought it was obviously a joke that one would use a browser to compiler another browser. The "on trusting trust" attack regards using your compiler as a mechanism to infect compiled executables -- including compilers themselves, and their generated code. I didn't mean to suggest that the two browsers shared any code.

mintplant 4y ago

There is actually some code sharing these days, mainly libraries. Mojo for IPC is the one I remember off the top of my head. I think also WebRTC stuff?

tristor 4y ago
Yes, in the strictest sense both browsers may rely on public open source libraries, which means they have some shared code, but they do not share any code directly with each other (e.g. Chrome is not a dependency of Firefox, Firefox is not a dependency of Chrome). I see this as not equating to "code sharing" because they both happen to use a library. Ironically for other apps that'd usually be something like OpenSSL, but in the case of Firefox and Chrome they actually have entirely separate TLS codebases as well (NSS for Firefox and BoringSSL for Chrome). For some of these shared open source libraries, either Mozilla or Google is the primary contributor/maintainer, and both organizations usually make contributions. This is true across many things, even libraries in the open source space that are not involved in the browsers themselves but may be in the toolchain (Mozilla has produced robust open source CI/CD tooling, bug trackers, etc over its history).
- deleted 4y ago
  [deleted]
fomine3 4y ago
Similarly ANGLE is made by Google (perhaps Chrome team) and now also used by Firefox

I_AM_A_SMURF 4y ago

I mean... the Firefox build has NodeJS in it now, so in a sense Chromium is in the toolchain :-)