As a fly on the wall during that period: @wycats and @littlecalculist considered Node/browser interop a top priority and tried (to the best of their abilities) to reach out. There was quite a bit of anti-TC39 sentiment at the time, and most feedback was "just use Node modules."
-
-
As I recall, they worked with
@izs quite a bit1 reply 0 retweets 1 like -
The anti-TC39 sentiment was never mine. I have had frustrations with it as with most committees, but that’s normal. A vocal minority of node users were assumed by some to speak for the project (1 of my frustrations). However, I believe esm is very good, if still incomplete…
1 reply 0 retweets 6 likes -
Node has dropped the ball with mjs and --experimental-modules, but that ball can still be picked up. The “esm” module is an implementation that does the right thing for both platforms. What’s remaining is to implement top level module identifiers (ie, packages) in a browser…
1 reply 0 retweets 14 likes -
And until then, we’re going to be relying on babel. Which, honestly, is fine, because everyone is using jsx anyway, which requires transpilation.
1 reply 0 retweets 4 likes -
1 reply 0 retweets 2 likes -
Replying to @slightlylate @rwaldron and
Idk what’s sad about that, really. It’s a short todo list, with extremely stable reference implementations already adopted by a majority of the js community. Seems like low hanging fruit, as cowpaths go.
2 replies 0 retweets 6 likes -
Hard fork of both JS and HTML syntax and semantics, sans same grammar. As bad as these ratholes ever go. You'd be better off redesigning regex syntax.
3 replies 0 retweets 6 likes -
Replying to @slightlylate @izs and
This sounds like an anti-Babel message. I feel like such a strong codemnationation of a widely used tool that is being actively encouraged by community leaders deserves a more finessed explanation - maybe a blog post?
2 replies 0 retweets 3 likes -
Replying to @robpalmer2 @slightlylate and
This is purely about JSX, not Babel, no?
2 replies 0 retweets 2 likes
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.