Re:How JavaScript works: an overview of the engine, runtime ...
by fenomas on Tuesday January 09, 2018 @12:32AM
(#16103858)
If the article had gone into any details I'd agree, but all it really says is that JS engines have a memory heap and a call stack. It doesn't get into the kind of depth where JS engines differ from one another.
Re:How JavaScript works: an overview of the engine, runtime ...
by blauditore on Tuesday January 09, 2018 @01:53AM
(#16104144)
Most of what's described here (mainly the call stack) isn't really JS-specific, but can be found in most high-level programming languages. (Are there even language implementations not utilizing a stack for function calls?)
I thought this would be much more specific to JS quirks.
Re:How JavaScript works: an overview of the engine, runtime ...
by tcarn on Monday January 08, 2018 @10:23PM
(#16103339)
What a fantastic breakdown. More developers really need to understand how the whole stack is interacting especially as we see the proliferation of server side js
Re:How JavaScript works: an overview of the engine, runtime ...
by jazzkingrt on Monday January 08, 2018 @10:26PM
(#16103361)
This post was helpful to me, as well as #4 of the same series: Event loop and the rise of Async programming
I come from a native programming background, and whenever I worked on front-end javascript I always felt I didn't quite grasp what's just behind the code.
These posts were a big help in getting rid of unknown unknowns.
While other Javascript engines may work in similar ways, the article doesn't make that assertion.
I thought this would be much more specific to JS quirks.
I come from a native programming background, and whenever I worked on front-end javascript I always felt I didn't quite grasp what's just behind the code.
These posts were a big help in getting rid of unknown unknowns.
https://blog.sessionstack.com/