As someone who uses Chrome under Mac, Windows and Linux I applaud this move.
The Quicktime plugin on Windows is HORRID. It is a prime example of how to make a user experience complete shit. And to be honest I'd prefer the Mac version not pull it in automatically either. Weither it's the crashing, slow startup times, bazaar buffering behavior or taking over way too many MIME types I hate it.
I strongly prefer that Chrome asked my permission before executing either the Quicktime or Java plugins just like it prompts for popups. All are annoying, buggy, laggy and crashy.
Both Quicktime and Java were manually disabled globally on every browser I use and now I can feel safe leaving them on. This change makes my web browsing experience SAFER and less frustrating.
Of course my dream is never to have to touch QuickTime or that horrid Apple Update garbage on Windows ever again. I'm not buying a Mac for home because Apple can't be trusted around VisualStudio.
Flash gets the pass because Adobe lets Google worry about making sure updates are available on day 1. Odds of Google and Apple working together on Quicktime... Haha... haha... ha.
QT on Windows is horrible, but disabling it outright and requiring users to start Chrome with a custom commandline, without warning and after an automatic (and hidden) update? Let's just say it did not go down well at work, where we use Chrome and QT for inhouse enterprise applications. I understand the need to push the envelope on web standards and that needs to happen at a rapid pace, but at least give us enterprise developers a chance to override it. Enterprises do not develop software at breakneck speed Google, it's just not worth it.
It handles QuickTime and Java the same way it handles Popups. It puts a yellow bar at the top asking for permission to "Run this time" or "Always run on this site".
Hit the "Always run on this site" button on Apple.com and your internal sites.
It's now "ask for permission to run" instead of "always run". It's in the same boat as intranet sites needing popup permissions.
Chrome clearly isn't made for the enterprise. IE has historically been a poor browser, but it gives sys admins quite a bit of control over how and when updates are applied.
I think the myth isn't that Chrome and Firefox don't offer enough control, but that such control is actually necessary. I suspect it is possible to build enterprisey systems that are robust enough to handle automatic browser updates.
Agreed. I think its something more than having an abysmal product like Quicktime. I like VLC a lot. But, I hate how its plugin takes over firefox if I allow it to. Most of these media player plugins for web browsers are extremely annoying.
The Quicktime plugin on Windows is HORRID. It is a prime example of how to make a user experience complete shit. And to be honest I'd prefer the Mac version not pull it in automatically either. Weither it's the crashing, slow startup times, bazaar buffering behavior or taking over way too many MIME types I hate it.
I strongly prefer that Chrome asked my permission before executing either the Quicktime or Java plugins just like it prompts for popups. All are annoying, buggy, laggy and crashy.
Both Quicktime and Java were manually disabled globally on every browser I use and now I can feel safe leaving them on. This change makes my web browsing experience SAFER and less frustrating.
Of course my dream is never to have to touch QuickTime or that horrid Apple Update garbage on Windows ever again. I'm not buying a Mac for home because Apple can't be trusted around VisualStudio.
Flash gets the pass because Adobe lets Google worry about making sure updates are available on day 1. Odds of Google and Apple working together on Quicktime... Haha... haha... ha.