[FEE-300] JavaScript Core & Runtime Overview
INFO
This category covers the JavaScript language and its runtime environment in the browser -- the execution model, scoping rules, asynchronous patterns, and memory behavior that every frontend engineer MUST understand.
Context
JavaScript is the only programming language natively supported by web browsers. Understanding its runtime model is essential -- not just the syntax, but how code actually executes: the single-threaded event loop, closure mechanics, prototype chain, and memory lifecycle. These fundamentals apply regardless of which framework you use.
Scenario
You are debugging an intermittent bug where a user's click handler fires correctly in Chrome but not in Safari, and a data fetch that works in one context silently fails in another. The symptom in both cases is the same: code that appears correct in isolation behaves unexpectedly in a specific runtime context. JavaScript's execution model — the event loop, the call stack, closures, and the prototype chain — determines how these interactions behave. Understanding the model is what separates fixing the symptom from fixing the cause.
Scope
This category covers:
- Event Loop & Async Model (FEE-301) -- How JavaScript schedules and executes code
- Closures & Scope Chain (FEE-302) -- How variables are resolved and retained
- Prototypes & inheritance (future)
- Type coercion & equality (future)
- Error handling patterns (future)
- Memory management & garbage collection (future)
Why This Matters
Framework abstractions hide the runtime. When something breaks -- a race condition, a memory leak, an unexpected this binding -- you need to reason about the engine, not the framework. Engineers who understand the runtime debug faster, write more predictable code, and make better architectural decisions.