> Surely it is Firefox' team's responsibility to use system calls in a sane way, say not almost 50x more than the competition? The docs for that function don't

> Surely it is Firefox' team's responsibility to use system calls in a sane way, say not almost 50x more than the competition? The docs for that function don't say anything about performance: https://learn.microsoft.com/en-us/windows/win32/api/memoryapi/nf-memoryapi-virtualprotect https://learn.microsoft.com/en-us/windows/win32/api/memoryap... They also don't say anything about "sane" usage, and while I don't have an MBA, I'm pretty sure they don't teach anything about `VirtualProtect` ratios when doing competitor analysis. One possibility is that the Chrome team's implementation was more efficient due to luck, or they invested the resources to identify the performance characteristics of this function call, whereas the Firefox team missed it. I don't think "Chrome has more development resources than Firefox" is news to anybody.