3 ms·

I must've imagined all the things like emscripten, all the new WebAPI's that make Firefox OS possible, WebRTC, asm.js, etc...but then again I'm not a random int

by gcp 13y ago

I must've imagined all the things like emscripten, all the new WebAPI's that make Firefox OS possible, WebRTC, asm.js, etc...but then again I'm not a random internet troll which is posting vague and baseless comments all over HN.

deleted 13y ago
[deleted]
rimantas 13y ago
emscripten depends on LLVM, guess who is the biggest backer of that project? Would you mind to expand a bit about "vague and baseless"? Or maybe you could spend some time and learn the history of canvas element, or CSS transforms? http://lists.w3.org/Archives/Public/www-style/2007Nov/0080.html http://lists.w3.org/Archives/Public/www-style/2007Nov/0080.h... http://lists.w3.org/Archives/Public/www-style/2007Nov/0090.html http://lists.w3.org/Archives/Public/www-style/2007Nov/0090.h... http://lists.w3.org/Archives/Public/public-whatwg-archive/2007Mar/0662.html http://lists.w3.org/Archives/Public/public-whatwg-archive/20... As for "all new WebAPI's" you'd be surprised how many of them were first implemented in WebKit. WebRTC? Chrome—fall 2012. Firefox—summer 2013
- gcp 13y ago
  As for "all new WebAPI's" you'd be surprised how many of them were first implemented in WebKit. Enlighten us: https://wiki.mozilla.org/WebAPI https://wiki.mozilla.org/WebAPI WebRTC? Chrome—fall 2012. Firefox—summer 2013 I don't think so: https://hacks.mozilla.org/2012/11/progress-update-on-webrtc-for-firefox-on-desktop/ https://hacks.mozilla.org/2012/11/progress-update-on-webrtc-... Note that at this point Firefox had DataChannel, and it would take Chrome months to catch up there. Firefox also introduced the used audio codec. That said it's a bad example, because WebRTC standardization is currently a strong effort between both companies and it'd be great for the web if more standards went this way rather than ending up with having to try to standardize half-assed implementations from one rendering engine. (cough WebSQL cough)

by gcp 13y ago

deleted 13y ago

[deleted]

rimantas 13y ago

emscripten depends on LLVM, guess who is the biggest backer of that project? Would you mind to expand a bit about "vague and baseless"? Or maybe you could spend some time and learn the history of canvas element, or CSS transforms? http://lists.w3.org/Archives/Public/www-style/2007Nov/0080.html http://lists.w3.org/Archives/Public/www-style/2007Nov/0080.h... http://lists.w3.org/Archives/Public/www-style/2007Nov/0090.html http://lists.w3.org/Archives/Public/www-style/2007Nov/0090.h... http://lists.w3.org/Archives/Public/public-whatwg-archive/2007Mar/0662.html http://lists.w3.org/Archives/Public/public-whatwg-archive/20... As for "all new WebAPI's" you'd be surprised how many of them were first implemented in WebKit. WebRTC? Chrome—fall 2012. Firefox—summer 2013

gcp 13y ago
As for "all new WebAPI's" you'd be surprised how many of them were first implemented in WebKit. Enlighten us: https://wiki.mozilla.org/WebAPI https://wiki.mozilla.org/WebAPI WebRTC? Chrome—fall 2012. Firefox—summer 2013 I don't think so: https://hacks.mozilla.org/2012/11/progress-update-on-webrtc-for-firefox-on-desktop/ https://hacks.mozilla.org/2012/11/progress-update-on-webrtc-... Note that at this point Firefox had DataChannel, and it would take Chrome months to catch up there. Firefox also introduced the used audio codec. That said it's a bad example, because WebRTC standardization is currently a strong effort between both companies and it'd be great for the web if more standards went this way rather than ending up with having to try to standardize half-assed implementations from one rendering engine. (cough WebSQL cough)