For those of you who for whom English is not your native language the word "can" does not mean "will." It just means that it is possible. Also, for those of us who use linux and relay on package management systems you should consult your distribution's documentation to see how to update your system.

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.

My logic is that only things that are actually interesting should be reported on. Have you noticed how often the linux, BSD, or other kernels are updated and how often Slashdot doesn't cover it? It's because it isn't news, and neither is this. I suspect the new owners of Slashdot were paid to put articles like this out. Chrome 24: Just like Chrome 23, only with a bigger number!

My logic is that only things that are actually interesting should be reported on.

Both you and I know this is extremely subjective.

It's a major release and as such it should be reported. Firefox also has a similar release schedule and it gets reported as much on Slashdot. I do find this new kind of release schedule (both on Chrome and Firefox) completely idiotic, but that's a whole different issue.

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

*sigh*
If the system load is high, they don't want to suck the CPU down any more (the update is a big CPU hog)
If the system is on a battery, they don't want to risk the update being aborted during an update if the battery dies.

If you are asking a rhetorical question that is the exact opposite of "just asking." Also, not everyone has Chrome installed and using it regularly, as well as paying attention to when updates occur, etc. That doesn't necessarily mean they don't want to know what is going on in the industry. Maybe I share a computer login and somebody else was using it when it updated. I could then decide to see if it already updated on its own, and force the update if it didn't.. I'm sure there are plenty of other reas

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? [caniuse.com] to see if any more css3 elements are now in widespread use so you can use them in web development.

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.

Are you confusing Chrome with Firefox? On my primary system I usually have Chrome running for weeks with like three or four dozen tabs. Many of which are some pretty resource intensive pages. Usually I only have problems after a week or two and then only with pages like tumblr archives that have 200 animated gifs on them visible at once.

I will concur though that some kind of tab overview would be great. Didn't early versions of Chrome have that?

In my experience, a freshly started Chrome needs way more memory for the same set of tabs than a freshly started Firefox. Firefox however leaks memory. That may or may not be caused by some plugin rather than Firefox itself but either way, I can only reclaim that memory by restarting FF.

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 li

I believe the next push will be to get extensions running on Chrome for Android. The major intent being to get Chrome Remote Desktop running on Android, allowing for TeamViewer-style remote control (NAT-traversal et al) of Windows, Mac and Linux boxes from your Android device. This can obviously be done already with third-party apps like TeamViewer or Splashtop; but this would bring it in-house and make it an OS feature.
As a side note, Splashtop used to use Google servers for NAT traversal. They release

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.

Have you seen the amount of state information that website commonly carry these days? It's been years since you could safely assume that if a user has "URL X" open, they will be OK with the browser just re-loading "URL X" at some point in the future. There's form data to consider, cookie stuff, URLs that don't point to any persistent resource on the server and are intended to time out fairly quickly, sites that are really picky about referrer strings(common on shitty multipage forms, breaks 'forward' and 'b

In any given week I might be working on 3 distinct projects at work, the most complex of which might have 4 or 5 distinct informational topics requiring reference material or research.

Each informational topic might require a web search or two, and anywhere from 3 to 10 pages from different sources to investigate the leads or to keep handy the valuable pertinent information for that work task.

Of course, we generally don't control for how long we get to continue working on a given task. An important priority

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:)

Why is Chrome on Android so much worse than Opera Mobile.
I'm actually at a point where I would be willing to pay Opera for its browser even though I manage to crash it every once in a while.
How long will it take for Firefox on Android to be worthwhile using? Checked 1.5 years ago. Rechecked a couple of weeks ago. There's been definite progress but it still has a long way ahead.

No, because Chrome updates tend to just work. Things don't break. I click Chrome and it works the same as it always had with the extensions it always has and it looks the same.

Everytime Firefox updates, things break. Either some extension I have suddenly doesn't work anymore, or more likely, someone changed something in the UI behavior so when muscle memory takes over, things go haywire.

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.

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.

For the very paranoid, there is a nice chromium variant. [comodo.com] Works well, doesn't freeze up like other options I've used, and the defaults make the IE10 "do not track" default look like an exibitionist.

Just firing it up, and it already tried to connect to several Google-owned domains (including the controversial gstatic.com) out-of-the-box without any warning or permission.

Attempting to just write text to the adress bar triggers another cascade of connections- initially to just activate the "aid" of predicting the site I am looking for, I know- but not stopping there. So where does it stop, exactly?

In addition, Chrome's UI is way too minimalistic for everyday use in my opinion, and completely uncustomizable. I detest having a close button on every tab - I regularly close Chrome tabs by accident - but they stubbornly refuse to do a damn thing about it.

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 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