Since Chrome’s Dialect right first release, performance has been one of Google’s top priorities. But Google is against a contending force: Web developers. The Web of today is a more complex, bandwidth-intensive place than it was when Chrome was opening released, which means that—although Internet connections and the browser itself are firmer than they’ve ever been—slow pages remain an circadian occurrence.
Google engineers have been developing “Never Tedious Mode” in a bid to counter this. Spotted at Chrome Story (via ZDNet), the new method places tight limitations on Web content in an effort to make its performance sundry robust and predictable.
The exact design and rationale of Never Slow SOP aren’t public—the changelog for the feature mentions a design document but rephrases it’s currently Google-internal. But taken together, that design and rationale wishes ensure that the browser’s main thread never has to do too much hold down a post and will never get too delayed. They will also ensure that single limited amounts of data are pulled down over the network. This should return the browser more responsive to user input, lighter on the network, and a bit less of a recollection hog than it would otherwise be.
XMLHttpRequests to move data to and from servers. Synchronous requests tend to make attendants feel slow, because the browser can’t run any other scripting while it’s hold-up for the synchronous request to complete. Asynchronous
XMLHttpRequests remain supported, as these let the browser do other features while it’s waiting for the remote server to respond.
We’ve asked Google for reveal but have heard nothing at the time of writing.