Slashdot Mirror

← Back to Stories (view on slashdot.org)

Visually Demonstrating Chrome's Rendering Speed

Posted by kdawson on from the want-to-see-it-again dept.

eldavojohn writes "Recent betas of Google's Chrome browser are getting seriously fast. Couple that with better hardware, on average, and it's getting down to speeds that are difficult to demonstrate in a way users can appreciate. Which is why Google felt that some Rube Goldberg-ish demonstrations with slo-mo are in order. Gone are the days of boring millisecond response time metrics."

1 of 140 comments (clear)

  1. Chrome is cheating... by stazeii · · Score: 4, Interesting

    Chrome is caching ALL content, even stuff that says "no-cache". While "no-cache" is somewhat broken, things like the horrible "Blackboard" web apps don't really work in Chrome because it's caching things that shouldn't be cached. If Google intends to do this, and encourage this with other browsers, they need to start teaching designers how to properly use caching headers so that Chrome doesn't break usability with it's aggressiveness.