@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@wycats@littlecalculist There's not just one JS type system that's right for everything people want to do with types.1 reply 0 retweets 1 like -
Replying to @samth
@samth certainly when you say "everything" its indisputable -- but remains to be seen if sth can manage most needs@wycats@littlecalculist2 replies 0 retweets 0 likes -
Replying to @lbljeffmo
@lbljeffmo@wycats@littlecalculist I think if we can't standardize the important stuff (the semantics) we shouldn't standardize anything.1 reply 0 retweets 0 likes -
Replying to @samth
@samth indeed -- that's mostly where we landed at the last mtg@wycats@littlecalculist1 reply 0 retweets 0 likes -
Replying to @lbljeffmo
@samth We agreed its ok to reserve space in grammar, but not grammar itself@wycats@littlecalculist3 replies 0 retweets 0 likes
@lbljeffmo @samth @littlecalculist and both metadata and "just ignore it" are future hostile to a 1JS future with types.
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.