Re:Node v8.1.2
by WorldMaker on Thursday June 15, 2017 @11:06AM
(#14561059)
A better term than virus is that async is a monad. Welcome to programming with monads. ;)
JS async produces Promises like C# produces Task, so you can call an async function and use the result as a Promise.
Can you wait for a promise synchronously? I am pretty new to JS so please forgive if this is a stupid question.
Re:Node v8.1.2
by WorldMaker on Thursday June 15, 2017 @11:43AM
(#14561434)
It's not something JS engines allow today. It's also not something that entirely makes sense from the perspective of a browser threading model or even the libuv-based NodeJS threading model.
I know. We have some wacky use cases where it would make sense. The real answer would probably be to say "Don't use Node for this" but that's a different discussion above my pay grade.
Re:Node v8.1.2
by WorldMaker on Thursday June 15, 2017 @03:06PM
(#14563437)
The real answer is probably "those places you think need to synchronous don't need to be synchronous" and you need a refactor or a rearchitecture.
Trust me. We are not totally stupid. We need synchronous actions under some circumstances.
> But it still beats promises or callback hell.....
And then() hell ...
But it still beats promises or callback hell.....