... The input from module developers is extremely valuable and needed ... As are other points of view...
-
-
... conflating the opinions of a few individuals with "many Node.js core devs" is very misleading...
2 replies 0 retweets 1 like -
Replying to @jasnell
Maybe it would be more accurate to say "The loudest, most persistent node devs are way too excited about breaking things"
3 replies 0 retweets 2 likes -
Replying to @feross
it really does not matter how loud one gets... On any side of the discussion...
1 reply 0 retweets 1 like -
... We are actively seeking a compromise path that is both reasonable and workable for the ecosystem...
2 replies 0 retweets 1 like -
Replying to @jasnell
Deprecating an API that has been in Node since the beginning for dubious "OMG DoS!!1" reasons is not reasonable or workable
3 replies 0 retweets 0 likes -
Replying to @feross
Has such a deprecation landed in core for that reason? We backed one out last summer specifically because it wasn't reasonable.
1 reply 0 retweets 0 likes -
again, be careful not to conflate the opinions of a couple individuals with the opinion of Node.js core.
1 reply 0 retweets 0 likes -
Replying to @jasnell
You said that you support deprecation in v9, so you're in that group of "a couple individuals" you know.
2 replies 0 retweets 0 likes -
I feel this debate has been going on for too long. Not enough moderation and decision making in threads. It's frustrating
1 reply 0 retweets 1 like
the infinite back and forth. The bloody frowny emojis and downvotes. For 4 months. It's like.. yeah not great
-
-
pushing decision making back means only the most committed people linger. We need to shut this proposal down. Yesterday
0 replies 0 retweets 2 likesThanks. Twitter will use this to make your timeline better. UndoUndo
-
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.