Slashdot Mirror

← Back to Stories (view on slashdot.org)

Google Tests 'Never-Slow Mode' for Speedier Browsing (zdnet.com)

Posted by msmash on from the up-next dept.

At some point in the future, Chrome may gain a new feature, dubbed 'Never-Slow Mode', which would trim heavy web pages to keep browsing fast. From a report: The prototype feature is referenced in a work-in-progress commit for the Chromium open-source project. With Never-Slow Mode enabled, it would "enforce per-interaction budgets designed to keep the main thread clean." The design document for Never-Slow Mode hasn't been made public. However, the feature's owner, Chrome developer Alex Russell, has provided a rough outline of how it would work to speed up web pages with large scripts. "Currently blocks large scripts, sets budgets for certain resource types (script, font, css, images), turns off document.write(), clobbers sync XHR, enables client-hints pervasively, and buffers resources without 'Content-Length' set," wrote Russell.

8 of 159 comments (clear)

  1. Que my mom wondering why the internets broke by Anonymous Coward · · Score: 5, Insightful

    Fucks sake - this is exactly the reason random web page X stops working.

    Here's a hint google: You're fixing the WRONG problem.

    The correct problem to apply pressure to:

    1) Crap web code, and specfically better educating the people that write it.
    2) Javascripts crappy threads.

    Your 'never slow mode' should only ever be a debug tool for people making web pages.

    1. Re:Que my mom wondering why the internets broke by DarkRookie2 · · Score: 4, Insightful

      Just look at the code for any site made or redesigned last 5 years.

      --
      http://progressquest.com/spoltog.php?name=Son+Of+Son+Of+DarkRookie
    2. Re:Que my mom wondering why the internets broke by dinfinity · · Score: 3, Informative

      You misspelled 'js' there.

      PHP is a server-side language, remember?

    3. Re:Que my mom wondering why the internets broke by swillden · · Score: 3, Insightful

      Your 'never slow mode' should only ever be a debug tool for people making web pages.

      I think the idea is that by making "slow mode" pages fail to work well, they'll force programmers to make better web pages. Chrome has had debug tools that provide all this information for ages, and the developers who make use of them can make very snappy sites. But those conscientious and careful developers aren't the problem. It's all the ones who won't do it right until doing it wrong results in user complaints that you need to reach.

      (Disclaimer: I work for Google but don't know anything about this beyond what I read in the summary. I didn't even RTFA.)

      --
      Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
    4. Re:Que my mom wondering why the internets broke by Dynedain · · Score: 3, Interesting

      The correct problem to apply pressure to:

      1) Crap web code, and specfically better educating the people that write it.
      2) Javascripts crappy threads.

      That's exactly what they're doing. If your site craps out under this mode, you'll be pressured to fix it.

      --
      I'm out of my mind right now, but feel free to leave a message.....
  2. Sounds like effective ad blocking is the answer by OffTheLip · · Score: 5, Insightful

    Web pages load okay without all of the crap added to them.

  3. How about tracking? by Anonymous Coward · · Score: 3, Insightful

    i would turn off the tracking and monitoring and everything would be much faster!

  4. Re:Go back to older HTML. by Fly+Swatter · · Score: 3, Insightful

    It would leave them where they belong - not in a web browser.