I mean we are talking right now. Disagreeme t does not mean I will shut you up in any way
-
-
Replying to @bradleymeck @satya164
I'm not questioning the legitimacy of the CTC to make the decision. But the choice implies nothing about technical quality.
2 replies 0 retweets 1 like -
1: It's too bad Node doesn't operate in a consensus-seeking fashion (or limits the seeking to elected reps?) because I still think
2 replies 0 retweets 0 likes -
I cant vote but CTC does seek quorum
1 reply 0 retweets 0 likes -
Browser rollout certainly affected things, so did handoff without impl of standard
1 reply 0 retweets 0 likes -
Replying to @bradleymeck @satya164
There is still a great deal of community concern about mjs. But it's screaming into the void because "The CTC Decides"
2 replies 0 retweets 1 like -
I'm by far not the only one concerned. The CTC has convinced itself it's necessary, which is repeated over and over when objections raised
2 replies 0 retweets 0 likes -
Don't you think it's concerning that there are people who've thought deeply abt this who don't share CTC's ostensibly technical conclusions?
1 reply 0 retweets 0 likes -
I think this spec is something that didnt seek consensus with community, resulting in problems. Now decisions must be made w. least dmg
2 replies 0 retweets 1 like -
Replying to @bradleymeck @satya164
1: See http://blog.izs.me/post/25906678790/on-es-6-modules …. We worked hard to collaborate. Ironically biggest issues (interop w/ default export) caused by designing
2 replies 0 retweets 1 like
2/2: for constraints raised by Node folks we were working with. Also see http://jsmodules.io/
-
-
Dont see a plan for node on that? Just that it is inspired?
0 replies 0 retweets 1 likeThanks. 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.