3 ms·
> Things like WebGL, NaCl, WebM/P, Dart VM, and various extension-only APIs that Chrome has introduced. Can someone explain this to me: why such a move, when p
by xentronium 15y ago
> Things like WebGL, NaCl, WebM/P, Dart VM, and various extension-only APIs that Chrome has introduced.
Can someone explain this to me: why such a move, when performed by microsoft is considered EEE (embrace, extend & extinguish) and when performed by google it suddenly becomes way to go?
- daleharvey 15y agoWebGL started at Mozilla, then Opera. Apple/Google/Mozilla and Opera are part of the working group that are developing it. WebM/P solved a problem that people have been asking for for years. Nacl and Dart could be considered EEE, but really the web has always been about experimenting to push tech as google are doing, all these technologies are open to be implemented elsewhere. Microsoft actively broke existing technologies and attempted to replace them with closed ones
- xentronium 15y agoYeah, my problem was with NaCl and DartVM, not WebGL/WebM. When developers start using <script type="text/dart"> scripts, they will break web for a huge segment of users. And NaCl is only marginally better than ActiveX. That's why I think both these technologies will not gain much recognition outside google and some cool side projects.
- beaumartinez 15y ago> Both these technologies will not gain much recognition outside google and some cool side projects ...Which is probably why there was little mention of "EEE" when they were announced—how can Google extinguish when nobody uses their alternative?