قالب وردپرس درنا توس
Home https://server7.kproxy.com/servlet/redirect.srv/sruj/smyrwpoii/p2/ Technology https://server7.kproxy.com/servlet/redirect.srv/sruj/smyrwpoii/p2/ With experimental "Never slow mode", Chrome tries to stop Web devs making it slow

With experimental "Never slow mode", Chrome tries to stop Web devs making it slow



  The word SLOW has been painted on a street in favor of drivers.
Enlarge / Google wants less of this.

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 ̵

1; slow pages remain an everyday event.

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.

In addition to capping various data sizes and limiting the time that JavaScripts can run, Never Slow Mode also blocks access to certain features that web pages can currently use, resulting in a performance cost. In particular, scripts are prohibited from using document.write () which is widely used by scripts to dynamically issue HTML (possibly including embedded CSS and JavaScript) to a page. They are also blocked from making synchronous 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.

The execution resources budget is reset every time a user interacts with the page. So every time a page is rolled or tapped, it can run a little more JavaScript and pull a little more data.

The size and execution time constraints are draconian, to say the least, and the JavaScript changes will break many existing pages. Together, they make Never Slow Mode a bit mysterious: This is not a condition that can be used for regular web browsing because the pages either run out of resources or depend on forbidden JavaScript. The current implementation of Never Slow Mode notes that it is only a prototype (with an "idiotic implementation" no less). So, regardless of its ultimate purpose, there is still much development left.

We've asked Google for comments, but haven't heard anything at the time of writing.


Source link