Chrome Release Cycle
docs.google.com
Chrome Release Cycle
1–10 of 30 posts
Re: Chrome Release Cycle
#2I've used chrome for about a year now. I've gotten so used to the seamless and silent updates that every other piece of software seems like nagware.
I'm sure I'd be singing a different tune if it broke my browser during a silent update.
Re: Chrome Release Cycle
#3One thing that helps Chrome release often is that the api for building extensions is all javascript. By comparison, Firefox extensions can have binary components. This means there needs to be a certain amount of platform stability or extensions will break every six weeks. I think that in the future we'll see faster release cycles for Firefox as the api for extension building becomes more js based and less dependent on xpcom components.
Re: Chrome Release Cycle
#4One 'problem' with this modus operandi is that some companies use the big releases as selling points. It is interesting that the Chrome team does not feel the pressure to do this. Especially considering how heated the browser war is these days. Everyone seems to think Firefox 4 is going to be the salvation, for example.
On the other hand, the silent updates are a blessing, and good features are another way of attracting users.
Re: Chrome Release Cycle
#5I've used chrome for about a year now. I've gotten so used to the seamless and silent updates that every other piece of software seems like nagware. I'm sure I'd be singing a different tune if it broke my browser during a silent update.
Lack of silent updates was one of the key reasons I switched from Firefox to Chrome (speed was another.) Seemed like every time I opened the browser to view a webpage I needed to see that very moment, Firefox would pop up an annoying update prompt that I'd keep clicking out of each time.
Re: Chrome Release Cycle
#6I've used chrome for about a year now. I've gotten so used to the seamless and silent updates that every other piece of software seems like nagware. I'm sure I'd be singing a different tune if it broke my browser during a silent update.
Lack of silent updates was one of the key reasons I switched from Firefox to Chrome (speed was another.) Seemed like every time I opened the browser to view a webpage I needed to see that very moment , Firefox would pop up an annoying update prompt that I'd keep clicking out of each time.
The funny thing is that from a Linux user's perspective, Google was simply providing a workaround for what should have been the OS's job. On Linux, Firefox's auto-updates are disabled so that the OS can handle that instead.
This is probably the best solution, as it gives you the most control over updates, and applies to all software system-wide. You're not forced to install updates at any time, and you can disable the notifications if you want.
Re: Chrome Release Cycle
#7One thing that helps Chrome release often is that the api for building extensions is all javascript. By comparison, Firefox extensions can have binary components. This means there needs to be a certain amount of platform stability or extensions will break every six weeks. I think that in the future we'll see faster release cycles for Firefox as the api for extension building becomes more js based and less dependent o…
I don't know about that. I would love to have an extension that made the omnibar a lot more like firefox's awesomebar (good indexing, can search for key phrases for title of article and the such) but to my knowledge that's pretty much impossible because of the javascript limitation (I hope I'm wrong here, not really sure).
I just wish google was a bit more subtle about wishing people search on google again when looking for previously viewed sites.
Re: Chrome Release Cycle
#8Earlier quoted context omitted.
Lack of silent updates was one of the key reasons I switched from Firefox to Chrome (speed was another.) Seemed like every time I opened the browser to view a webpage I needed to see that very moment , Firefox would pop up an annoying update prompt that I'd keep clicking out of each time.
The funny thing is that from a Linux user's perspective, Google was simply providing a workaround for what should have been the OS's job. On Linux, Firefox's auto-updates are disabled so that the OS can handle that instead. This is probably the best solution, as it gives you the most control over updates, and applies to all software system-wide. You're not forced to install updates at any time, and you can disable th…
The update popup for extensions is still annoying though - even on linux.
Re: Chrome Release Cycle
#9One 'problem' with this modus operandi is that some companies use the big releases as selling points. It is interesting that the Chrome team does not feel the pressure to do this. Especially considering how heated the browser war is these days. Everyone seems to think Firefox 4 is going to be the salvation, for example. On the other hand, the silent updates are a blessing, and good features are another way of attract…
Well, Google does make some noise about releases. I forget which version (proving your point) of Chrome brought the Store, but at the time it was touted by version number, despite the silent update. Probably something we'll see more of as companies move to the cloud and mobile.
Re: Chrome Release Cycle
#10Earlier quoted context omitted.
The funny thing is that from a Linux user's perspective, Google was simply providing a workaround for what should have been the OS's job. On Linux, Firefox's auto-updates are disabled so that the OS can handle that instead. This is probably the best solution, as it gives you the most control over updates, and applies to all software system-wide. You're not forced to install updates at any time, and you can disable th…
The update popup for extensions is still annoying though - even on linux.
Like I said, you can disable that.