@slightlylate As I recall you told me there was an intent to expose UDP / TCP Socket APIs to PWAs, where can I read more about the current plan ? And are these APIs being currently considered https://www.w3.org/TR/tcp-udp-sockets/ … ? Thanks
-
-
-
Replying to @slightlylate @inexorabletash
Could you please share once it's established ? I would like to use that towards making a case on our end.
3 replies 0 retweets 2 likes -
I should also note that they're annoyingly different from Node and I hope a future version would be more compatible with the larger JS ecosystem so I could waste less time writing bizarro browser compatibility shims.
1 reply 0 retweets 1 like -
I'm afraid in that regard without cooperation from node we can't really get far. So far they have being deliberately choosing to not adopt emerged standards and stay incompatible. Modules & Streams are two top off my head.
1 reply 0 retweets 0 likes -
Were they participants in that process? From a user perspective it seems like basically neither side pays much attention to the other.
1 reply 0 retweets 0 likes -
NPM is a member http://www.ecma-international.org/memento/sme.htm of TC39. Node does not appear to be
Whatwg also has open participation. Generally though web browsers participate in standardization & often make uneasy compromises in the process, in my observation node's attitude is
1 reply 0 retweets 0 likes -
To be fare I have not being very engaged with node for quite some time so my observations could be outdated. Although I still think that not embracing ES modules, Streams, Typed Arrays (fully) is a mistake. I'm sure there are plenty of arguments not to.
2 replies 0 retweets 0 likes -
My understanding is that the Node steering committee has made a relatively large change in this regard and that web compat is now a goal.
1 reply 0 retweets 1 like
It's unclear the extent to which this is informed by the preponderance of Node and NPM users deploying these tools in service of frontend development, but it's welcome regardless.
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.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.