2 ms·
That’s super impressive. I didn’t expect a compiler setting change to make up the difference between Chrome and Safari. Has anyone experimented with even more
by skavi 5y ago
That’s super impressive. I didn’t expect a compiler setting change to make up the difference between Chrome and Safari.
Has anyone experimented with even more aggressive compiler options? Targeting specific chips or using fat LTO?
I wonder if any of Apple’s former lead was due to them being able to target specific computers.
I’ll have to download Chrome again and see if the power usage is up to par with Safari.
- alwillis 5y agoIt’s more than compiler settings; Google’s been focusing on performance for a while. I suspect Apple will reclaim the performance lead once Safari 16 at WWDC in June.