3 ms·
It doesn't exactly need to be Chrome-specific; every browser/JS engine will have slightly different performance on different workloads, so Google just has to le
by yjftsjthsd-h 7y ago
It doesn't exactly need to be Chrome-specific; every browser/JS engine will have slightly different performance on different workloads, so Google just has to lean heavily on things that are golden-path for Chrome. They could even do this accidentally/nonmaliciously just by mostly testing on Chrome and not testing performance on other browsers.
- derf_ 7y ago> They could even do this accidentally/nonmaliciously Designing a development process that naturally achieves a malicious outcome is just as bad as actively making malicious decisions: https://www.zdnet.com/article/former-mozilla-exec-google-has-sabotaged-firefox-for-years/ https://www.zdnet.com/article/former-mozilla-exec-google-has...
- afiori 7y agoWouldn't it rather be "Maintaining and not fixing" rather than "Designing"? Google is perfectly allowed to make mistakes or forget something. The criticism is that this is a repeated behavior, as if they decided that it is never going to be a priority.