Re:Show HN: Nsynjs – JS engine with stoppable threads and wi...
by balfirevic on Wednesday May 24, 2017 @06:48AM
(#14409003)
Why would you need to know, except in some special cases? If you're using async/await, your next line is not executing anyway until the result comes, blocking or not.
Re:Show HN: Nsynjs – JS engine with stoppable threads and wi...
by sametmax on Wednesday May 24, 2017 @08:58AM
(#14409646)
Because otherwise you block the even loop or mismatch life cycle. Espacially reading an unfamiliar code base.
Re:Show HN: Nsynjs – JS engine with stoppable threads and wi...
by z3t4 on Wednesday May 24, 2017 @06:57AM
(#14409034)
embrace higher-order functions. Use named functions and closures!
example code:
var anchors = document.getElementsByTagName(“a”);
for(var i=0,len=anchors.length; i<len; i++){
alertClickAnchor(i); // Named function
}
function alertClickAnchor(i) { // Closure
anchors[i].onclick = function() {
alert(i);
}
}
If you have transparent async, then:
Then how do you know what blocks and what doesn't ? What's asynchronous and what's going to trigger a switch ? What's a disguised callback and what's the next line ?
What's the solution then ?