Slashdot Mirror
Chrome Should Get 'Extremely Fast' at Loading a Whole Lot of Web Pages (cnet.com)
Chrome is going to get a big speed boost -- at least for web pages you've recently visited. CNET: With a feature called bfcache -- backward-forward cache -- Google's web browser will store a website's state as you navigate to a new page. If you then go back to that page, Chrome will reconstitute it rapidly instead of having to reconstruct it from scratch. Then, if you retrace your steps forward again, Chrome will likewise rapidly pull that web page out of its memory cache. The speed boost doesn't help when visiting new websites. But this kind of navigation is very common: Going back accounts for 19 percent of pages viewed on Chrome for Android and 10 percent on Chrome for personal computers, Google said. With bfcache, that becomes "extremely fast."
before everyone became concerned with "expiring pages" and made it so you couldn't go back without re-posting data. Then they made it so you couldn't even view the page source without reposting data.
So, we're going back to what we had 10 years ago?
As usual, someone else is insisting on what the users REALLY want. The financial models don't really make it possible to do otherwise, eh?
Let me put it this way: If you had the option to donate $10 toward the implementation of this feature, would you? What feature do you actually want instead? Wouldn't it be nice if someone cared enough to ask?
ADSAuPR, atAJG.
Freedom = (Meaningful - Coerced) Choice != (Speech | Beer^2), and sad sock puppets' bad mods avail them naught.
Firefox does throttle CPU in background tabs. For a very long time APIs like setTimeout have been throttled aggressively.
There has been quite recent work on using OS APIs to reduce the priority of processes running background tabs: https://bugzilla.mozilla.org/s...
No. The Pi-hole is a DNS blackhole for ads, beacons, and trackers. Anything in the subscription list is simply blackholed from being called to my network. This does wonders for bandwidth, and every device that connects to my network is protected. Raspberry Pi 3B+, case, 32GB SD card, Ethernet cable, and about an hour of time. Best thing I've done lately (almost a year ago) for my network. I run Raspbian. I bought the complete Cana Kit on Amazon for like $69.
But this kind of navigation is very common:
Not for me. When I'm viewing a page that has multiple sub-pages of interest, I tend to open a new tab for those sub pages. For example, one tab for the /. main page and a new tab for each article I read -- similarly for actual news sites. :-) Don't really know why I would want to go back and forth within a single tab.
It must have been something you assimilated. . . .
I back this up.
Pi-Hole regularly blocks between 60 - 80% of my internet traffic with daily browsing, and down to about 40 - 50% when I'm working.
It definitely increases browsing speed, page performance, resource usage, etc
Thanks for your insight. To make it easier on us in the future can you please list in alphabetical order all the things you don't use so we don't accidentally bother you again?
Due to your brevity, I'm not sure if you were deliberately being insightful or it was some sort of joke. However, it is true that the economic model is driving the behaviors, but only indirectly in this case through the google's invasive ad business. Even from that perspective there are other options for new features that make much more sense than this.
If the user is dissatisfied with the speed, they can buy a faster Internet connection or a faster computer or both. Much more than $10 in such cases.
Error in the original Subject. Last part should have been "Me neither."
Freedom = (Meaningful - Coerced) Choice != (Speech | Beer^2), and sad sock puppets' bad mods avail them naught.
Yea but the revolutionary breakthrough here is that Google found a way to patent it so now nobody else can do it anymore without paying them royalties.
Only Alt-Right people would do such a thing.
Escher was the first MC and Giger invented the HR department.
A way to increase font sizes without breaking page layouts on poorly programmed sites.
Browser caching has been a source of many headaches in our org with regard to CMS's and dynamic web applications. You can put header tags that allegedly turn off caching so users always see the latest, but they don't always work right on all content types (HTML, images, CSS, JavaScript, PDF's, etc.). All browser brands we've tested have at least one caching bug.
If browser makers haven't perfected current caching, then this new fancy-ass caching will probably have even more bugs.
Table-ized A.I.
That's not Google's business model, never has been. Since it's going into Chromium, Google is open sourcing it.
This space intentionally left blank
yes, it does... in the past it cached the page, so back would fetch it from cache and was still log faster, specially because network was so slow. Several years ago (maybe 7 or 8 years ago), they started to cache also the already rendered page, so back would not even need to re-rendering most of the cached data
Higuita
Opera Presto (which is to say, versions 7 through 12) had this years ago, though the early versions didn't handle dynamic pages well. It was one of their stronger features, and when they did change it most people wanted the option to put it back the way it was. It doesn't do anything for javascript/HTML benchmarks as it only deals with pages you've seen before, but it helps immensely on workflow.
,,, until you (hopefully) find what you want. With this RAM cache (as Opera called it), returning to the results page is as fast as if you'd just switched tabs, so you don't need to open the links in new tabs (and thus don't use as much memory and CPU).
Best example, you do a search and get a results page, then have to look at the pages in the results to see if they are what you're looking for. So you load one page, then go back to the results page, then load the next
Well, there are two or three ways of doing this. Storing all the fields, storing final DOM, and never deleting the active page, but just putting it to sleep.
Safari and Firefox has been doing the latter since 2003 or so, but will fall back to one of the others under memory pressure or when the entry is old enough in history, and this is what Google is now implementing 17 years later.
I'm a little confused here. WebKit has had a back-forward cache for as long as I can remember, and Chrome forked off of that. How is this not already part of Chrome?
The WebKit implementation was incompatible with their multi-process model, so they had to rewrite it. Though I am kind of shocked they didn't do this YEARS ago.