Chrome 24 Released, Chrome Beta Channel For Android Added
An anonymous reader writes "Google has released Chrome version 24 for Windows, Mac, and Linux. You can update to the latest release now using the browser's built-in silent updater, or download it directly from google.com/chrome. The biggest improvement on the user side of things is the speed increase. Google's own Octane JavaScript test shows that this is the fastest Chrome release yet. When the beta came out in November, the company was touting that Chrome had become 26 percent faster on Octane than it was last year. Now it's even faster. Google also announced it is introducing a new Chrome beta channel for phones and tablets running Android 4.0 or higher. You can download version 25.0.1364.8 right now directly from Google Play (since this is a beta, it's not available via search; you'll need to use the link). The release of version 25 is significant because it means Google is attempting to bring Chrome for Android in line with the desktop version. The current release of Chrome for Android is version 18, last updated in November."
I am posting with from:
Google Chrome 25.0.1364.5 (Official Build 174090) dev
OS Linux
WebKit 537.22 (@138211)
JavaScript V8 3.15.11.2
With silent update the meaning of these announcements is that it is time to check Can I Use? to see if any more css3 elements are now in widespread use so you can use them in web development.
Work bio at MMWD
Managing memory better so I don't have to keep shutting down web browsers every day or two. Most power users have many windows and many tabs up, and some are relevant for weeks, but most are unused and could be backgrounded much more effectively in terms of processor and memory use. Hint: Replace with a URL and a snapshot image updated infrequently.
Also, speaking of tabs. If I use them, I can't easily see visually which pages I have up, in the overview of windows display modes that most OSs offer. There is a usability disconnect here.
Where are we going and why are we in a handbasket?
By your logic, Chrome should've been mentioned by Slashdot only once, during it's initial release, since it includes a silent updater from day 1.
Between mobile Firefox being a thing again and Chrome being improved we can finally see some competition for Opera Mobile on Android :)
The state of the Android browser is fairly pathetic, so this is really quite important.
Right now the only reason for chromebooks to exist is that Chrome on Android is meh at best. When this changes they can stop deploying ChromeOS. Hopefully they will offer some kind of upgrade path to Android on Chromebooks, so that the community doesn't have to fumble its way through :)
"You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
You don't. You can force the update. Otherwise it will update with it's next scheduled check.
I've noticed that for large SVG files where much of the content has display='none' (so it is only displayed when something is clicked to trigger a change in the display property) Chrome seems to take several seconds to become responsive after the SVG page load is initiated, while other browsers seem to handle it almost instantly. Since a display value of none "indicates that the given element and its children shall not be rendered directly (i.e., those elements are not present in the rendering tree)" it seems Chrome shouldn't be spending so much time processing such stuff. Version 24 doesn't seem to fix that issue.
I'll wait for Chrome 31.1 for Workgroups. Hurr durr.
Chrome's functionality sounds great, but I do not like its attitude: it establishes numerous connections "on the side" talking back to Google central all the time, almost constantly transmitting all sorts of information: Google intercepts and highjacks most of the traffic when someone uses Chrome, that much is obvious.
The three laws of thermodynamics:(1) You can't win. (2) You can't break even. (3) You can't even quit.
My understanding is that the silent update mechanism checks in with the mothership periodically, either as-scheduled or with some consideration for system load/onbattery vs. on AC/etc. The Chrome release team has their own schedule that the update mechanism has no knowledge of.
So, if your silent update mechanism is active, you will automatically receive the newest release; but only when the updater next phones home. Depending on when it last phoned home and when the release occurs, this might be a matter of several days. If you force a check it should happen about as fast as bandwidth allows.
Even if an undisplayed element is not in the rendering tree, it's still in the DOM.
With these kind of release numbers, 100 is a more appropriate major release.
Some people don't like bookmarks, or they use their browser like "todo" lists.
Not that I advocate such an approach, but I understand it.
For any particular project I might have a handful of links that are open at one time.
I typically don't have 100 tabs open, but 20-40 is pretty typical.