@getify @rreverser @marijnjh You're comparing the usage of the web to a developer tool like Babel?
-
-
Replying to @sebmck
@sebmck@rreverser@marijnjh when tools choose standards adherence (for interop), more tools in ecosystem win.2 replies 0 retweets 0 likes -
Replying to @getify
@getify@rreverser@marijnjh What tools? I keep on hearing this but have no clear examples of where this actually works out.2 replies 0 retweets 0 likes -
Replying to @RReverser
@rreverser@getify@marijnjh No there obviously were. You keep on talking about this invisible pipeline that Babel needs to integrate with2 replies 0 retweets 1 like -
Replying to @sebmck
@sebmck@rreverser@marijnjh ex: i wanted to build a 2-way style formatter (inbound and outbound rules)1 reply 0 retweets 0 likes -
Replying to @getify
@sebmck@rreverser@marijnjh tool requires CST (which was not standardized)… but inbound could be babel, or outbound could be babel1 reply 0 retweets 0 likes -
Replying to @getify
@sebmck@rreverser@marijnjh example pipeline: let-er (my tool) -> esre (my tool) -> babel -> uglify2 replies 0 retweets 1 like -
Replying to @getify
@sebmck@rreverser@marijnjh but for that pipeline to work, i need a parser on the front that has standard CST, and ...1 reply 0 retweets 0 likes -
Replying to @getify
@sebmck@rreverser@marijnjh the outbound pipe (to uglify or babel) needs to also support the same tree.1 reply 0 retweets 0 likes
@getify @rreverser @marijnjh It basically comes down to that this hasn't worked (it's what it's like today)
-
-
Replying to @sebmck
@sebmck@rreverser@marijnjh it hasn't worked, b/c the big players have never committed to making it work.2 replies 0 retweets 0 likes - 3 more replies
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.
he/him 