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."
You can update to the latest release now using the browser's built-in silent updater. Not really silent if you need to be told you need to update.
You can update to the latest release now using the browser's built-in silent updater...
If it's a silent updater, why do we need press releases for new versions? I'm just asking, since Slashdot seems to be less about tech news and more about regurgitating press releases lately.
#fuckbeta #iamslashdot #dicemustdie
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?
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.'"
I still think it's really neat that I can click install in the Play Store on my PC and watch it start downloading on my phone...
Good, now can I have my goddamn side tabs back?
You don't. You can force the update. Otherwise it will update with it's next scheduled check.
And people get irrationally upset about Firefox's release schedule?
It still only feels like Chrome 23 was just released last week.
When will the insanity stop? It's getting incredibly tiring.
In Chrome 24.0.1312.52 m, stringA.localecompare(stringB) throws an exception from their internationalization code. Worked on Chrome23 and other browsers.
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.
when do we get the opposite of "google chrome"?
which would (i guess) be a slimy slow html server for free?
obviously we all have no idea how the database of google works, but we all know how HTML should (baring all adobe flash).
so it's either use all google servers or we can do our own? sh1t this is a perversion taken to extrems :
Worth noting that this release 100% breaks monitor color profile support, which sucks if you're someone that cares about photos. It's incredible that this is not a more important to the Chrome developers, but maybe most people don't care about quality. Just speed.
Before this release, you had to use the --enable-monitor-profile command-line switch to enable monitor profile support. It wasn't perfect but it worked most of the time. Now this does nothing. Lame.
What are you doing that you need a tab open for weeks? During a session I'll have some tabs open and when I'm finished close the browser. What are these people doing with 100 tabs open at a time?
Only the State obtains its revenue by coercion. - Murray Rothbard
If it's a silent updater, why do we need press releases for new versions?
Perhaps the press release is intended for web developers, to let them know that they can design web applications around the new features.
[Insert well-articulated, well-reasoned comment that can be boiled down to "Chrome SUXS! Firefox FTW"]
Even if an undisplayed element is not in the rendering tree, it's still in the DOM.
Based on the version #, I assume Chrome 1.0 came out some time in the mid-80s, possibly much earlier.
What I want is for them to fix Crome's broken printing. I've had no end of problems printing from within Chrome. I realize it works for many people but not for us. Their default print preview will not print multiple copies, ignores color settings, sometimes ignores duplex settings, and has other problems besides. I've had problems and so has at least one other person in our company. We have to use the system dialog each time we print. I've sent in some problem reports but nothing has seemed to update in the last 6 months.
Not really silent if you need to be told you need to update.
How can Google let Firefox 18 know they are 6 majors releases behind in the browser wars if they update silently?
They might have released 24 versions now but have you seen Word? That's up to version 2013.
Chrome 24 breaks the use of animations in GWT 2.4 compiled code. If Google truly backs both of these products, they'll hopefully issue a Chrome patch ASAP. For more information see http://code.google.com/p/chromium/issues/detail?id=158910
They've got opus audio for their remote desktop feature and WebRTC last I heard, but they STILL haven't added support for it in plain old tags...
Hacker Public Radio is our Friend
Teach me to blindly click "post" - that's "Opus in support", for "plain old " (html5) tags.
Hacker Public Radio is our Friend
when are they going to create a secure password generator? Lastpass is great but it would be so much smoother cross device if Chrome handled it all.
It's incredible that this is not a more important to the Chrome developers,
No its not, because,
most people don't care about [color profiles].
(FTFY)
I dont know of anyone (outside of IT colleagues) who would even know what a color profile is. I dont know that Ive ever used one, or that I care to.
The one bug that has turned me off with Google Chrome was the bug that kept the window on top no matter what. This is a very annoying bug and it needs to be fixed immediately.
http://productforums.google.com/forum/#!topic/chrome/EjI1gnwXaZQ
https://productforums.google.com/forum/?fromgroups=#!topic/chrome/HP1kNhXGMqs
Firefox crashes way too often for my taste, but since about version 13 it's gotten a lot better on memory use. I haven't used Chrome in a while, just tried it and found that yeah, it's really really fast. It used to be a real memory hog, and I won't be able to tell if that's still true unless I load it up with a lot of tabs. (And unfortunately, since I'm stuck running 32-bit Win7, I can't just throw enough virtual or real memory onto the laptop to handle memory bloat, and modern browsers don't seem to like waiting for Win7 paging anyway.)
Bill Stewart
New Fast-Compression-only CPR http://preview.tinyurl.com/dy575ks
Worth noting that this release 100% breaks monitor color profile support, which sucks if you're someone that cares about photos. It's incredible that this is not a more important to the Chrome developers, but maybe most people don't care about quality. Just speed.
Before this release, you had to use the --enable-monitor-profile command-line switch to enable monitor profile support. It wasn't perfect but it worked most of the time. Now this does nothing. Lame.
I think its terrible that thery removed this feature! As a photographer it makes it really hard to assess what my prints look like on line now
It's troll or overrated when I say it, it's insightful when someone agrees
I love slashdot
"You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"