简体中文
EnglishHow The Modern JavaScript Tutorial relates to manuals and specifications
Updated
The Modern JavaScript Tutorial (javascript.info) is a learning resource, not a reference. It explains JavaScript concepts step by step with examples and tasks, and it deliberately keeps environment-specific notes to a minimum so you learn the language itself. Manuals and specifications, by contrast, are authoritative reference documents: you consult them to confirm exact behavior, not to learn from scratch. The tutorial even has a dedicated section, "Manuals and specifications," that explains this relationship and points readers to the official sources.
What each resource is for
| Resource | Primary purpose | How you use it |
|---|---|---|
| The Modern JavaScript Tutorial | Teach concepts progressively with explanations, examples, and tasks | Read sequentially, do the exercises, build understanding |
| Manuals (e.g., MDN-style references) | Describe methods, properties, and APIs in lookup form | Search for a specific method or object when you need details |
| Specifications (e.g., ECMAScript spec) | Define the exact, normative behavior of the language | Check edge cases, algorithm steps, and precise semantics |
The tutorial's own framing is that it concentrates on the language itself, "with the minimum of environment-specific notes." That tells you what to expect: deep coverage of core JavaScript (closures, prototypes, classes, promises, async/await, modules, and more), but not a complete catalog of browser or Node.js APIs.
Why the tutorial includes a "Manuals and specifications" section
That section exists because learners eventually hit questions the tutorial cannot answer exhaustively. A tutorial can explain how Array.prototype.map works and when to use it; a manual lists its parameters and return value; the specification defines the exact steps the engine must follow. The tutorial's role is to get you to the point where reading the other two is productive rather than overwhelming.
How to use them together
- Learn the concept in the tutorial first. Work through the relevant chapter and its tasks. For example, study the Promises and async/await chapters before trying to interpret specification text about promise resolution.
- Use a manual for day-to-day lookup. When you need a method signature or a quick reminder, a manual is faster than re-reading a chapter.
- Reach for the specification when behavior is surprising. If code behaves unexpectedly at the edges, the spec is where the exact rules live.
- Return to the tutorial for structure. The table of contents is organized as a learning path — JavaScript language, then browser document/events/interfaces, then additional articles — which a manual or spec does not provide.
Practical caveats
- The tutorial is not a substitute for the specification when correctness at the margins matters; it teaches, it does not define.
- Manuals and specifications are not substitutes for the tutorial when you are starting out; they assume you already know the surrounding concepts.
- Because the tutorial minimizes environment-specific notes, expect to consult other sources for DOM APIs, Node.js, or tooling beyond what its browser-focused part covers.
If your goal is to learn JavaScript from the ground up, start with the tutorial. Keep a manual open for lookups, and treat the specification as the final authority when you need to know exactly what the language does.