3 ms·
I'm guessing there was renewed urgency for responsiveness due to 120fps displays on M1 mac's - which made lower frame rates compared to Safari more noticeable.
by etaioinshrdlu 5y ago
I'm guessing there was renewed urgency for responsiveness due to 120fps displays on M1 mac's - which made lower frame rates compared to Safari more noticeable.
- zamadatix 5y agoSeems like an unlikely driver in it's own, especially considering those didn't show up until near the end of this time period. Meanwhile Chrome has been needing to run more power efficiently at similar refresh rates and pixel counts on Android devices all the same. Of course ARM Android devices don't have Safari to compare to nor are they a new platform ripe with as many low hanging fruit optimizations so it's not going to be the lead topic here. The truth is this is the same kind of stuff Chrome (and any browser) has been working on since the software launched. Regardless of which devices come out nobody has ever said "I like that this browser is slower and less efficient than the other".