It's much more common and accepted to use hoisted function declarations. Warning: It’s not common or a good idea to rely on variable hoisting to use a variable earlier in its scope than its var declaration appears it can be quite confusing. This appendix aims to give you some challenging and interesting exercises to test and solidify your understanding of the main topics from this book. In terms of incorporating hoisting in your code, here’s a tip from “ You Don’t Know JS”: You Don't Know JS Yet: Scope & Closures - 2nd Edition Appendix B: Practice.

But I find this explanation more convincing, though I haven’t checked the source myself. I heard some say hoisting was introduced back in the old days to make writing JavaScript easy (heh). There are automatic optimizations that help alleviate this (tail calls optimizations), but they are not yet supported everywhere and work only in simple cases. We can rely on it being 10000, some engines allow more, but 100000 is probably out of limit for the majority of them. This does not work for function expressions. The maximal recursion depth is limited by JavaScript engine. See the code below and guess its behaviour: var n = 10 function hoistingTest() If you haven’t come across it, seeing an example is probably the best way to understand the behaviour. Coming across hoisting was one of my first ‘WTF’ moments when learning JavaScript.

You dont know js recursion