There will be new threads about how the streams and other standard classes dealing with IO need to be rewritten/expanded to work well with async. I've been using async/await for about a year now(in node.js, much longer in C#) and took to wrapping them when needed; you find various levels of difficulty depending on how much eventing is involved. All the information hidden away in non-public properties/api's doesn't help. MS had to go through and expand out all their stuff with Async methods. I wonder how long the node.js maintainers will take..
Async/await, let, and TypeScript have made node.js bearable for me but, TBH, I'd rather be working with Go or C# more. Owell, right tool for the job and all which has a temporal component as well.
Async/await, let, and TypeScript have made node.js bearable for me but, TBH, I'd rather be working with Go or C# more. Owell, right tool for the job and all which has a temporal component as well.