> At first, they touted the maneuver as being all about supporting “open” formats. But if that’s the case, why not pull support for the Flash plug-in baked into every version of Chrome currently? This is the single shittiest argument I've ever heard, and continue to hear. 1) Adobe isn't charging browser makers royalty or licensing fees to use Flash. 2) Are we really going to pull the "all or nothing" argument with a…
It is not.
Users and developers are free to use any and all Flash components. Flash itself is a published standard (although proprietary). You can create alternative VMs largely w/o caveat (the only one i've heard raised was some DRM junk having to do with Flash Media Server, which no one should use anyway).
There is no threat of patent licensing hovering over people who use Flash. That is not the case with H.264 encoding.
Furthermore, it is obnoxious that Flash is always uncritically trotted out as the only example of proprietary components in Chrome. What about Java plugins? Anything you want to say about Flash you can say about Java applets.
Please stop spreading FUD.
Also, Google didn't own WebM 5 years ago. It's hardly sensible for criticizing them for not moving more quickly on the issue.