4 ms·

From the linked bug: > I think I can reproduce this behavior on Figma's code base too. I've never noticed because we use Chrome pretty much exclusively for dev

From the linked bug: > I think I can reproduce this behavior on Figma's code base too. I've never noticed because we use Chrome pretty much exclusively for development. We're already there. Chrome dominates so much of the dev market, so naturally v8 is what people are optimising towards.

thirtyseven 6y ago
Don't worry, everyone still has to test for the captive audience of iOS Webkit users.
kjksf 6y ago
In this particular case, they were not optimizing for Chrome. They generated the code that was obvious to generate. Because of a perf bug in WebKit they added a flag to generate less correct code that is fast in WebKit. If anything, it's a case of optimizing towards WebKit. But really, it's a case of performance bug in WebKit and them adding a work-around.