2 ms·
Sorry, by resources, I meant real resources building an implementation of H.264 and supporting that in an official capacity, and assisting Adobe's implementatio
by jasonlotito 16y ago
Sorry, by resources, I meant real resources building an implementation of H.264 and supporting that in an official capacity, and assisting Adobe's implementation of Flash. I'm pretty sure that the resources needed to implement H.264 was on a different scale then providing assistance with Adobe.
This all ignores the fact that Google's involvement was improving the plugin experience alongside Mozilla, and it wasn't just benefit Flash.
Even still, all this is to say that it's still Adobe's version of Flash that goes into Chrome. Google isn't writing their own Flash implementation. What this means is that someone could build and H.264 plugin for Chrome. Google just doesn't want to be the person to do this. Considering the fact that handling this plugin would likely cost them money, I don't see a problem with their decision.