I imagine the likes of Babel currently hide all of this in the Node context, but is there a move to either change the standard API to async/await, or provide a standard mirror API?
Either option sounds full of compatibility / maintainability headaches, so how does Node get from its current state of callback hell out the box to async / await?
goroutines aren't magically turning async calls into sync, just hiding them deeper "under the hood"; there must be hope for Node.
> is there a move to either change the standard API to async/await
From what I remember there was no plans to change that (based on discussion from couple of months ago by node members on github).
> Either option sounds full of compatibility / maintainability headaches
It is.
> goroutines aren't magically turning async calls into sync, just hiding them deeper "under the hood"; there must be hope for Node.
Of course it's not about turning code into sync one, it's about coding style to look like it would be a sync one. But in case of Go it was created with this as main language concept, everything was designed around it, scheduling, user space lightweight stacks for gorutines etc.
Either option sounds full of compatibility / maintainability headaches, so how does Node get from its current state of callback hell out the box to async / await?
goroutines aren't magically turning async calls into sync, just hiding them deeper "under the hood"; there must be hope for Node.