> careful what you wish for here, see: NPM / Node ecosystem) Just to be clear, I think the NPM ecosystem is generally great and a massive success. People tota

> careful what you wish for here, see: NPM / Node ecosystem) Just to be clear, I think the NPM ecosystem is generally great and a massive success. People totally overblow the issues, and none of them are actually because of a small std library or due to the ease of install/publish. > however, it is worth identifying when something is becoming / has become / is considered to be such a core feature of the ecosystem that it would benefit greatly from stdlib support, I agree, and I think that there are a few places with regards to async that could work well here. Maybe some kind of Executor trait (hard, but maybe possible?), probably `std::block_on`. > see all the talk about async Rust in the communicate, FWIW I think the majority of people are just happily doing async work in Rust and don't get too involved in the discussions. I'm one of those people, except I'm also an internet addict on extended PTO so here I am. > All this is to say, maybe its time to seriously start thinking about what first party support will look if we bring in a first party async / non-blocking I/O platform into the stdlib I agree, I think some of this is best done in the language but some should be in std. No question.