Earlier quoted context omitted.
I feel as though you overlooked the "every" word in my question. I appreciate you built once, that's a solid accomplishment. If I'm going to be riding your custom build, with your custom C++ changes that introduce their own RCE risk, I want to at least know I'm only vulnerable to your RCE and not your RCE plus the 'just disclosed' RCE for Chromium itself that was actually patched 3 weeks ago but that you didn't bothe…
i think you raise a good point but also... how else would you propose to "fork Chrome"? this seems like the most reasonable approach?
It's also not a rando library that changes 3 times a year and who fucking cares if it has vulns: this is one of the biggest attack surfaces known to mankind given what it does for the user
Merely as a "for comparison," rebuilding Firefox takes about an hour on a developer class workstation, which IMHO sure would make tracking upstream a lot less expensive