HN Explorer

12 comments

[ 3.1 ms ] story [ 37.3 ms ] thread
tcarn
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
jazzkingrt
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.

jluse
JavaScript: Understanding the Weird Parts by Anthony Alicea is also really helpful and similar to this post check it out if you can :)
mproud
I would hope the free plan let’s me get started for free.
ChrisSD
This is a good post but I feel like the title is misleading. It's specifically talking about the V8 engine in particular, not Javascript in general.

While other Javascript engines may work in similar ways, the article doesn't make that assertion.

fenomas
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.
blauditore
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.

pjmlp
Yes, there are calling conventions that can do everything via registers, assuming a certain size threshold.