--- title: How JavaScript learned to cheat — A Deep Dive into the... description: A detailed walkthrough of how JavaScript engines execute code, covering the full pipeline from source text to optimized machine code. Explains lexing, AST... canonical: https://daily.dev/posts/how-javascript-learned-to-cheat-a-deep-dive-into-the-js-engine-aqrk9b7iq twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: How JavaScript learned to cheat — A Deep Dive into the JS Engine | daily.dev og:description: A detailed walkthrough of how JavaScript engines execute code, covering the full pipeline from source text to optimized machine code. Explains lexing, AST... og:url: https://daily.dev/posts/how-javascript-learned-to-cheat-a-deep-dive-into-the-js-engine-aqrk9b7iq og:image: https://api.daily.dev/og/posts/AqrK9B7iq.png og:image:alt: How JavaScript learned to cheat — A Deep Dive into the JS Engine og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # How JavaScript learned to cheat — A Deep Dive into the JS Engine **[Medium](https://daily.dev/sources/medium_js)** · 14 min read · 1 upvotes · 0 comments ## Summary A detailed walkthrough of how JavaScript engines execute code, covering the full pipeline from source text to optimized machine code. Explains lexing, AST parsing, bytecode generation, and V8's multi-tier compilation strategy (Ignition, Sparkplug, Maglev, TurboFan). Covers JIT compilation mechanics, speculative optimization, deoptimization triggers (monomorphic vs megamorphic call sites), hidden classes and dictionary mode, and generational garbage collection. Includes practical tips for writing JIT-friendly code such as keeping types consistent and object shapes stable. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### What is the difference between monomorphic, polymorphic, and megamorphic call sites in V8? A monomorphic call site always receives the same argument types and gets fully optimized by TurboFan. A polymorphic call site receives two or three different type combinations, forcing TurboFan to generate code handling multiple cases, which is slower. A megamorphic call site receives many different types, causing TurboFan to give up optimizing entirely and fall back to a generic, slow execution path. _Developers chasing hot-loop performance bugs can dig deeper into V8 optimization patterns on daily.dev._ ### Why does V8 deoptimize a function and what triggers it? V8 deoptimizes a function when a speculative assumption made by TurboFan breaks, such as calling a function previously optimized for numeric arguments with strings instead. The engine throws out the compiled machine code, falls back to the Ignition interpreter, and restarts profiling. Soft deopts allow reoptimization later, while hard (eager) deopts mark the code path so V8 refuses to speculate on it again. _Anyone debugging inconsistent JS performance can track engine behavior details like this on daily.dev._ ### What are V8's compiler tiers and what does each one do? V8 uses four tiers: Ignition interprets bytecode with no optimization for cold code; Sparkplug quickly compiles warm functions to baseline machine code with no speculation; Maglev, introduced in 2023, applies mid-tier speculative optimizations like assuming numeric types for hot code; and TurboFan performs heavy, aggressive optimization such as type specialization, inlining, and register allocation for functions called tens of thousands of times consistently. _Developers optimizing JS runtime performance can follow engine internals coverage like this on daily.dev._ ## Similar posts on daily.dev - [How JS Works — Part 3: JavaScript Optimization Strategies](https://daily.dev/posts/how-js-works-part-3-javascript-optimization-strategies-mnkuhaedz) · Medium · 3 upvotes · 0 comments - [V8 Engine: The Journey of JavaScript from Code to Execution](https://daily.dev/posts/v8-engine-the-journey-of-javascript-from-code-to-execution-junca4frw) · JavaScript in Plain English · 0 upvotes · 0 comments - [Think Like the JavaScript Engine](https://daily.dev/posts/think-like-the-javascript-engine-xvugilfs6) · freeCodeCamp · 87 upvotes · 5 comments - [JavaScript engines zoo](https://daily.dev/posts/javascript-engines-zoo-in2kjwont) · Hacker News · 1 upvotes · 0 comments --- Tags: [#javascript](https://daily.dev/tags/javascript), [#v8](https://daily.dev/tags/v8), [#compiler-optimization](https://daily.dev/tags/compiler-optimization) [View this post on daily.dev](https://daily.dev/posts/how-javascript-learned-to-cheat-a-deep-dive-into-the-js-engine-aqrk9b7iq) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"How JavaScript learned to cheat — A Deep Dive into the JS Engine","url":"https://daily.dev/posts/how-javascript-learned-to-cheat-a-deep-dive-into-the-js-engine-aqrk9b7iq","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/how-javascript-learned-to-cheat-a-deep-dive-into-the-js-engine-aqrk9b7iq"},"datePublished":"2026-07-20T20:07:18.650Z","dateModified":"2026-09-14T06:49:36.631Z","description":"A detailed walkthrough of how JavaScript engines execute code, covering the full pipeline from source text to optimized machine code. Explains lexing, AST...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/ca2be554c0e604a703146cda01fdc078?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/ca2be554c0e604a703146cda01fdc078?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Medium","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Medium","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/medium","url":"https://daily.dev/sources/medium_js"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/how-javascript-learned-to-cheat-a-deep-dive-into-the-js-engine-aqrk9b7iq","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":1},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"javascript,v8,compiler-optimization","timeRequired":"PT14M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Medium","item":"https://daily.dev/sources/medium_js"},{"@type":"ListItem","position":3,"name":"How JavaScript learned to cheat — A Deep Dive into the JS Engine"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/how-javascript-learned-to-cheat-a-deep-dive-into-the-js-engine-aqrk9b7iq#faq","mainEntity":[{"@type":"Question","name":"What is the difference between monomorphic, polymorphic, and megamorphic call sites in V8?","acceptedAnswer":{"@type":"Answer","text":"A monomorphic call site always receives the same argument types and gets fully optimized by TurboFan. A polymorphic call site receives two or three different type combinations, forcing TurboFan to generate code handling multiple cases, which is slower. A megamorphic call site receives many different types, causing TurboFan to give up optimizing entirely and fall back to a generic, slow execution path. Developers chasing hot-loop performance bugs can dig deeper into V8 optimization patterns on daily.dev."}},{"@type":"Question","name":"Why does V8 deoptimize a function and what triggers it?","acceptedAnswer":{"@type":"Answer","text":"V8 deoptimizes a function when a speculative assumption made by TurboFan breaks, such as calling a function previously optimized for numeric arguments with strings instead. The engine throws out the compiled machine code, falls back to the Ignition interpreter, and restarts profiling. Soft deopts allow reoptimization later, while hard (eager) deopts mark the code path so V8 refuses to speculate on it again. Anyone debugging inconsistent JS performance can track engine behavior details like this on daily.dev."}},{"@type":"Question","name":"What are V8's compiler tiers and what does each one do?","acceptedAnswer":{"@type":"Answer","text":"V8 uses four tiers: Ignition interprets bytecode with no optimization for cold code; Sparkplug quickly compiles warm functions to baseline machine code with no speculation; Maglev, introduced in 2023, applies mid-tier speculative optimizations like assuming numeric types for hot code; and TurboFan performs heavy, aggressive optimization such as type specialization, inlining, and register allocation for functions called tens of thousands of times consistently. Developers optimizing JS runtime performance can follow engine internals coverage like this on daily.dev."}}]} ```