Since Chrome's first release has been performance has been one of Google's top priorities. But Google is against a competing force: Web developers. Today's Web is a more complex, bandwidth-intensive site than it was when Chrome was first released, which means that while Internet connections and browsers themselves are faster than they have ever been ̵
Google engineers have developed "Never Slow Mode" in an attempt to counter this. The mockery of Chrome Story (via ZDNet) puts the new state's tight restrictions on web content in an effort to make its performance more robust and predictable.
The exact design and reason for Never Slow Mode is not public-changelog for the Feature mentions a design document, but says it is currently Google-internal. But overall, the design and the grounds will ensure that the browser's main thread never has to do too much work and never gets too late. They will also ensure that only limited amounts of data are pulled down over the network. This should make the browser more responsive to user input, easier on the network and a little less of a memory hay than it would otherwise be.
XMLHttpRequests to transfer data to and from servers. Synchronous requests tend to make pages feel slow because the browser cannot run other scripting while waiting for the synchronous query to fill. Asynchronous
XMLHttpRequests remains supported as these allow the browser to do other things while waiting for the remote server to respond.
We've asked Google for comments, but haven't heard anything at the time of writing.