@rreverser @sebmck babel's apparent stance: "all previous interop attempts failed, and will continue to fail, until we absorb them all"
-
-
Replying to @getify
@rreverser@sebmck which is a vote to say "standards processes failed, so let's invent our own" (hence my "NIH" earlier)2 replies 0 retweets 3 likes -
Replying to @getify
@rreverser@sebmck btw, in that world, until/unless babel announces full support for usable CST, all the tools i want to build are DOA.2 replies 0 retweets 0 likes -
Replying to @AdamRackis
@adamrackis i didn't ever insinuate he did. the point is, the ESTree standards process was working on this problem. he is not.2 replies 0 retweets 0 likes -
Replying to @getify
@getify ESTree was my idea. Nobody gave a shit about this interoperability until I bought it up in the Esprima call.@adamrackis3 replies 0 retweets 0 likes -
Replying to @sebmck
@sebmck Hm? "Nobody gave a shit"? ES6 was just beginning to appear and if you're talking about new node types.@getify@adamrackis2 replies 0 retweets 1 like -
Replying to @RReverser
@sebmck I'm grateful for you speaking about need for this from Babel side, but that exact statement was unfair.@getify@adamrackis2 replies 0 retweets 0 likes -
Replying to @RReverser
@rreverser@sebmck the babel tool is great. none of us are shitting on it. but i don't agree w/ your stance on interop.1 reply 0 retweets 0 likes -
Replying to @getify
@rreverser@sebmck and, as i said personally, that stance could spell failure, or at least much longer delay, in a 5-yr quest of my own2 replies 0 retweets 0 likes
@getify @rreverser Babel isn't even a year old. There's more than enough time to find out whether or not my idea works and if not, it dies.
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.
he/him 