@wycats @brendaneich The platforms we have, today, and have shipped apps on for decades, are much better than asm.js + new JS APIs.
@landonfuller @BrendanEich Let's get to work then. Those APIs need to be developed as standards because we can't expose POSIX/Windows.
-
-
@wycats@landonfuller Security rules unconstrained datagram sending out, raw sockets to any host ditto, but WebRTC has p2p APIs incl. UDP. -
@wycats@landonfuller Point that should be clear by now: no pixie dust for native; safety not optional on web; almost all else expressible. -
@BrendanEich@wycats@landonfuller hot tip: always bet on JS.
End of conversation
New conversation -
-
-
@wycats@landonfuller missed WebUSB + RawSockets (in Firefox OS, stdization far out; safety + lack of other vendor interest), also WebAudio? -
@BrendanEich@wycats Doesn't that just demonstrate that Firefox is willing to stick its neck out on non-standardized Firefox OS APIs? -
@landonfuller All browsers do this. Mozilla writes draft specs, tries to win&keep consensus. FxOS-led APIs in WebKit via Tizen.@wycats
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.