Chrome 10 released
Chrome 10 released
Posted Mar 9, 2011 17:20 UTC (Wed) by rillian (subscriber, #11344)Parent article: Chrome 10 released
Posted Mar 9, 2011 17:23 UTC (Wed)
by clugstj (subscriber, #4020)
[Link] (12 responses)
Posted Mar 9, 2011 17:42 UTC (Wed)
by Kit (guest, #55925)
[Link] (10 responses)
Chrome's development model is just extremely aggressive and fast paced, and after using it extensively for quite a while, I've never had a single stability issue with it, or even it just acting 'funky'.
Posted Mar 9, 2011 18:49 UTC (Wed)
by rillian (subscriber, #11344)
[Link] (9 responses)
Posted Mar 9, 2011 19:03 UTC (Wed)
by Kit (guest, #55925)
[Link] (8 responses)
Posted Mar 9, 2011 19:53 UTC (Wed)
by rillian (subscriber, #11344)
[Link] (7 responses)
I can think of a number of reasons why one might not update a particular application: dependence on specific behaviour, audit status, uniformity within an organization--none of which depend on one's facility with Chromium's build system.
Certainly it may be advantageous to subscribe to software updates from any given source, and open source provides great advantage in this because many parties can provide alternate or competing formulations of the same basic software.
Open standards allow even broader alternatives. Firefox is also a web browser, and it has not implemented this kind of testing, nor do they require automatic updates--although many of their developers would benefit from it--precisely because their focus is on user control and freedom.
Posted Mar 9, 2011 20:03 UTC (Wed)
by drag (guest, #31333)
[Link] (2 responses)
Yeah, how many are those actually legit? Seems most of it is just paranoia and being stuck with crappy internal websites more then anything else.
But....
I don't know how accurate this still is, Chrome annoyingly changes stuff and with all the excitement around it and the long long beta some documentation is way out of date... but pulling from a quick 'google':
Windows: Disable auto update through a registry key. This can be deployed via active directory group policies or other sane mechanism. If your managing lots of Windows systems and are not using AD, may God help you.. cause nobody else will. (until Samba4 reaches a stable release, of course.) :-P
MacOS: You can disable it through the 'defaults' command.
Linux: Chrome just uses the regular package management system. If you can't figure out how to disable automatic updates with that then you have serious problems. :-D
Posted Mar 9, 2011 22:40 UTC (Wed)
by johndrinkwater (guest, #65840)
[Link] (1 responses)
Posted Mar 9, 2011 23:59 UTC (Wed)
by drag (guest, #31333)
[Link]
It's important to them, bless them, but it's mostly irrelevant for my purposes.
Posted Mar 9, 2011 20:33 UTC (Wed)
by Kit (guest, #55925)
[Link] (2 responses)
First off, what do you mean by 'this kind of testing'? Chrome's "testing" situation is similar to that of Debian than anything else: Stable vs Stable channel, Testing vs Beta channel, Unstable vs Dev Channel, features move down into Stable from Dev, via Beta (and there's also another Canary channel added a while back, closer to nightly builds).
Also, if you don't want Chrome to automatically update, just install the Standalone version: http://www.google.com/chrome/eula.html?standalone=1
In addition, Firefox also has an auto-updater- it's just less user friendly (it'll interrupt your work multiple times, and won't work if you're not an administrator/root... and last I checked, it wouldn't even automatically notify you of updates in those situations!).
Posted Mar 9, 2011 21:14 UTC (Wed)
by rillian (subscriber, #11344)
[Link]
I also see I generally failed to make my point. There's a common itch to want to just take over management of everything for the convenience and benefit of one's users. And that's a great impulse while it really is beneficial. But like any situation were many people give power over themselves to a small group, it can easily become abusive. To the extent that we're Free Software advocates, it behooves us to watch such situations carefully and make sure real choice is in fact easy and available.
Posted Mar 11, 2011 3:29 UTC (Fri)
by jonabbey (guest, #2736)
[Link]
Posted Mar 9, 2011 23:46 UTC (Wed)
by robert_s (subscriber, #42402)
[Link]
The biggest one I've found is testing. I discovered a bug in a webapp of mine with chrome which I didn't remember seeing before. So I needed to find out whether this was a bug in my code or a recently introduced bug in chrome. Of course, all the windows test machines I had access to had magically updated themselves to the latest chrome version, and I couldn't find any real way of testing against an older chrome.
I won't touch Chrome on any of my (real) systems because of its behaviour. Google treat the user's PC like another one of their websites. Theirs to do whatever they want with whenever they want.
Life with transparently self-updating applications is like living in a state of permanent amnesia.
Posted Mar 9, 2011 22:37 UTC (Wed)
by einstein (subscriber, #2052)
[Link]
Nope, the reason it's at version 10 is that it's the 10th iteration of the browser. There are no gaps in the succession of version numbers. 9 was stable and 10 was beta, now 10 is stable and 11 is beta, and so on.
Chrome 10 released
Chrome 10 released
Chrome 10 released
Chrome 10 released
Chrome 10 released
Chrome 10 released
Chrome 10 released
So I can understand the reason people would want to hold on to older insecure browsers that just bloody work.
Chrome 10 released
Chrome 10 released
> testing, nor do they require automatic updates--although many of their
> developers would benefit from it--precisely because their focus is on user
> control and freedom.
Chrome 10 released
Chrome 10 released
Chrome 10 released
Chrome 10 released