Is that not what we have seen multiple times in meetings? Sometimes there is no concrete path forward
-
-
Not really sure why you made this an attack on a completely separate standards org... I guess this is why I try to avoid @-ing you...
-
I was literally repeating text that you tweeted minutes ago.
-
We're going to (or should) be making updated proposal to browser field spec to include WASM/ASM as well. We want resolution seemless
-
I say one takes a W3C community group approach similar to how
@jfbastien has successfully ran the WASM CG. Leave WG to stamping approve.
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.