3 ms·
People keep confusing this it seems. What Google is doing here is NOT like what Microsoft did. Google is merely implement many new HTML5 features ahead of Micro
by higherpurpose 12y ago
People keep confusing this it seems. What Google is doing here is NOT like what Microsoft did. Google is merely implement many new HTML5 features ahead of Microsoft (which is usually the most behind in HTML5 support) and others.
So it's not that they are "built for Chrome". It's that they are built for "new HTML5 specs" and only Chrome happens to support them right now. Point me to where Silverlight was an HTML spec?
Now, things like NaCl on the other hand are a lot more similar to what Microsoft used to do, but there's still a major difference, and that is that what they are building is open source and everyone can do their own implementation of it. You could never do that with ActiveX or Silverlight. Plus, you could also say Firefox is doing the same as Google with asm.js, which nobody else has adopted so far.
These things are a little more like that, but at least they are open source. The HTML5 features, though, just happen to be implemented faster by Chrome.
- tkinom 12y ago> "at least they are open source" Kinda of remind me of how "open" android is progressing. More and more "features" are pushing into "google experience" layers - also look at how open is the android TV. BTW, chrome is doing the same on the extension side. I see the pro/con on the "extension move" - reduce the security risk , etc. But it is sure feel like the Jedi master is feeling the power of the dark side - "working within the system" is not as fun as just being the Empire.