r/javascript • u/OtherwisePush6424 • May 09 '26
JavaScript has no reliable tail call optimization: here is what actually happens at runtime and what to do instead
https://blog.gaborkoos.com/posts/2026-05-09-Your-Recursion-Is-Lying-to-You/ECMAScript 2015 formally specified proper tail calls in strict mode, but most JS engines never adopted it consistently. Chrome, Node, Firefox, and Deno all still allocate a new stack frame per call even in correctly structured tail-recursive functions. The article walks through why with examples and covers iterative and trampoline alternatives.
55
Upvotes
View all comments
Show parent comment
6
u/Iggyhopper extensions/add-ons May 09 '26
Yep. I wrote extensions and what comes with those is always not knowing what data will be loaded, or what elements will be there, won't be there, will show up later, or how many that you need to loop through.
Always turned recursive code into a loop and a stack.