I don't see any reason to believe that changes are "no longer possible"
-
-
Replying to @wycats @bradleymeck and
cool, get TC39 to consider the constraints of non-browser JS platform
3 replies 0 retweets 0 likes -
Replying to @Fishrock123 @wycats and
It is not in node's best interests to implement and encourage ...
1 reply 0 retweets 0 likes -
Replying to @Fishrock123 @wycats and
... solely using a new package system which removes functionality ...
2 replies 0 retweets 0 likes -
Replying to @Fishrock123 @wycats and
... which has extensive use in the wild, and cannot be replicated ...
1 reply 0 retweets 0 likes -
Replying to @Fishrock123 @bradleymeck and
it sounds like you already arrived at a conclusion, and therefore assume we don't care
2 replies 0 retweets 0 likes -
Replying to @wycats @Fishrock123 and
we all have things we care about; let's get together & try to find a soln we can all live with
1 reply 0 retweets 0 likes -
Replying to @wycats @Fishrock123 and
seriously, node success with modules is and has always been a top priority 1/
2 replies 0 retweets 0 likes -
Replying to @wycats @Fishrock123 and
goes back to when
@izs was first raising issues, and vendors continue to ship behind a flag 2/1 reply 0 retweets 0 likes -
as I said yesterday, last time I had a long conversation with
@littlecalculist, we entertained radical changes 3/1 reply 0 retweets 0 likes
but we need to work together to find a soln; @littlecalculist, @caridy and I can't figure out node ourselves 4/4
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.