not getting the 1st change you wanted doesn't mean you're being blocked. Means we need to work harder
-
-
I don't believe there is time to do anything if implementations are rolling out behind flags already
2 replies 0 retweets 0 likes -
Replying to @bradleymeck @wycats and
but this is just 1 (not event top 3) of the problems inhttps://github.com/tc39/agendas/pull/214 …
2 replies 0 retweets 0 likes -
Replying to @bradleymeck
--
@tomdale asked you why you aren't working with me and@littlecalculist. You said "any disagreement is enough to block" 1/1 reply 0 retweets 0 likes -
Replying to @wycats @bradleymeck and
now you're pointing to a list of concerns that you never once reached out to us to discuss 2/
2 replies 0 retweets 0 likes -
except all those time in hangouts, gchat, irc, ...
1 reply 0 retweets 0 likes -
Replying to @bradleymeck @wycats and
the fact that it is on the agenda is largely because Node got a seat on TC39 and felt agenda \1
2 replies 0 retweets 0 likes -
Replying to @bradleymeck @tomdale
-
@littlecalculist and I have a track record of listening to node concerns and making chnageshttp://blog.izs.me/post/25906678790/on-es-6-modules …1 reply 1 retweet 4 likes -
Replying to @wycats @bradleymeck and
whether or not node got a seat on TC39, we consider node adoption of modules to be a top priority
3 replies 4 retweets 7 likes -
Replying to @wycats @bradleymeck and
@thealphanerd at the cost of everything else, sure. Nice. Say more.1 reply 0 retweets 0 likes
what do you mean?
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.