I really hope we've still got time. Seems like node core is dragging their feet because everyone knows deep down it's a really bad idea.
-
-
I really hope so. They're touting GitHub adopting .mjs in GitHub pages as some kind of success story.
1 reply 0 retweets 1 like -
fwiw I did see Bradley say that .mjs was "written in stone" - which sucks. But hey, just use
@jdalton's loader and move on!3 replies 0 retweets 2 likes -
Replying to @AdamRackis @mjackson and
The frustrating thing about node is no consensus process. I've been forced to sling proposals over the wall for years.
1 reply 1 retweet 6 likes -
Replying to @wycats @AdamRackis and
"we voted, we're done" - not how consensus works.
1 reply 1 retweet 7 likes -
Replying to @wycats @AdamRackis and
Aside: I have noticed you &
@littlecalculist advocate consensus over voting also in TC39, etc. Are there long-form posts explaining why?2 replies 0 retweets 1 like -
Replying to @robpalmer2 @wycats and
We talk about this with each other a lot. It'd be a good topic for a blog post.
1 reply 0 retweets 1 like -
Replying to @littlecalculist @robpalmer2 and
IMO consensus is the best way to do it. "Standards" should follow the lead of people solving real problems, not the other way around.
2 replies 0 retweets 7 likes -
Replying to @mjackson @littlecalculist and
The biggest disappointment of my professional life is that everyday problem solvers often do not drive standards. /
@ken_wheeler2 replies 2 retweets 7 likes -
Replying to @AdamRackis @mjackson and
(TC39 being a happy exception, with outstanding results to show for it)
1 reply 1 retweet 5 likes
Partnership between problem solvers and implementors always produces the best results. Should happen more.
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.