2 ms·
> They were at no point comparing the latest version of Safari against a year old version of Chrome. They tend to update that page after a Safari update, which
by bla3 5y ago
> They were at no point comparing the latest version of Safari against a year old version of Chrome.
They tend to update that page after a Safari update, which is yearly. They tend to highlight benchmarks that Safari looks good in. If Chrome and Firefox then optimize these highlighted benchmarks and catch up on these benchmarks within a month, Apple still has that page show the old data for a year. And for next year's release they again pick the benchmarks that look best for them at that moment in time and keep the numbers up for a year. Even though this update cadence guarantees that the numbers are outdated and misleading for the majority of the time they're up.
- soraminazuki 5y ago> They tend to update that page after a Safari update, which is yearly So you very well knew Apple weren't "comparing against a one-year old version." > And for next year's release they again pick the benchmarks that look best for them at that moment in time They're using the exact same benchmarks as last year, and the numbers seem to be improving for Safari. May I remind you I actually checked the past version of Apple's website on the Wayback Machine?
- invisible 5y agoI'm not the GP author, but I don't think they actually said that _exactly_. I agree it was a bit vague, but the latter point of them using an old version of Chrome for their most recent update was more pertinent. They are comparing a pre-release to a stable in both cases and then not spending any effort to contrast that later.