@wycats I'm almost positive the discussion at last mtg was focused on syntax reservation, if thats what youre ref-ing to?@littlecalculist
-
-
Replying to @lbljeffmo
@lbljeffmo I heard many heartfelt requests in the past two meetings to rapidly move towards more ambitious goals.@littlecalculist1 reply 0 retweets 0 likes -
Replying to @wycats
@wycats really? I heard discussion about what it would take to get there. That seems pretty healthy to me@littlecalculist2 replies 0 retweets 0 likes -
Replying to @lbljeffmo
@lbljeffmo I think spending much time on standardizing types ("manifest destiny" or no) is extremely premature.@littlecalculist1 reply 0 retweets 0 likes -
Replying to @wycats
@wycats I think we (tc39) need to facilitate moving in the direction of a std TSys. Very diff from stdizing a TSys ASAP@littlecalculist3 replies 0 retweets 2 likes -
Replying to @lbljeffmo
@lbljeffmo I don't think the ecosystem needs or benefits much from TC39's bureaucratic stamp of approval to work on this@littlecalculist2 replies 0 retweets 0 likes -
Replying to @wycats
@wycats Working with means tc39 pays attn so it knows before it might do sthing that gets in the way.@littlecalculist2 replies 0 retweets 0 likes -
Replying to @lbljeffmo
@lbljeffmo Plenty of ppl on TC39 are doing userland type systems. Easy to avoid future hostility without seal of approval@littlecalculist2 replies 0 retweets 0 likes -
Replying to @wycats
@wycats@lbljeffmo@littlecalculist As I understand it, the champion model is about working without needing a seal of approval for details.3 replies 0 retweets 1 like -
Replying to @sebmarkbage
@wycats@lbljeffmo@littlecalculist I actually think JS type systems are far away from being really good, but so were modules initially...1 reply 0 retweets 0 likes
@sebmarkbage the ES6 process sucked. Let's not do that again. @lbljeffmo @littlecalculist
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.