2 ms·
I'm not sure why you are being downvoted, because you are technically correct - a lot of Firefox developers use VS Code, which is based on Chrome and it is part
by 323 4y ago
I'm not sure why you are being downvoted, because you are technically correct - a lot of Firefox developers use VS Code, which is based on Chrome and it is part of the toolchain.
ELI5: are you really sure that when you work on Firefox source code from VS Code, that what ends up in the saved file and what gets committed to Git is what you actually see on screen?
- wyldfire 4y agoI think I was just a bit too subtle with my joke. VSCode doesn't seem like a "on trusting trust" attack vector since we can easily observe the git outputs of the C/C++ source and these parts often reviewed by peers. Unlike object code -- we can always take a look at the disassembly but in practice it's not scrutinized. It's probably frustrating to those who work on Firefox to suggest that it somehow depends on Chrome. I get that. But it wasn't where I was going. There is some kinda-out-there reality though -- with something like WASM or v8 you can theoretically run real toolchains like gcc and clang "in the browser". ;)
- 323 4y agoThere are 100% VS Code workflows - you edit in VS Code, commit from VS Code, and do code reviews from VS Code and review GitHub issues from VS Code. > frustrating to those who work on Firefox to suggest that it somehow depends on Chrome. Maybe those developers should not look too closely at who ultimately pays their salaries :)
- easrng 4y agoClang has been compiled to WASM: https://wapm.io/syrusakbary/clang https://wapm.io/syrusakbary/clang