Show notes
You have seen it in error messages: "Maximum call stack size exceeded."
But do you know what the call stack actually is?
In this episode, Alex Vega explains how JavaScript keeps track of where
it is as your code runs — through a simple analogy that makes the whole
thing click.
By the end, you will know how to read a stack trace, why stack
overflows happen, and why JavaScript can only do one thing at a time.
Oh, That's Why. — JavaScript, finally making sense.
Here is the medium article https://medium.com/@gize.bonilla/0674b29aeb1a
References
http://latentflip.com/loupe
Website: podcasters.spotify.com
