The Editor Landscape
Text Editors & IDEs Survey
Chapter 1 · The Editor Landscape
This course exists to cover a real gap: editors and IDEs beyond what's already owned elsewhere on this site. Before covering anything new, it's worth being explicit about exactly what's already covered — and why this course deliberately doesn't repeat it.
What This Course Deliberately Skips
Vim already has its own two-course track (Learning Vim, Vim Intermediate/Advanced) — modal editing, motions, and real depth already live there. VS Code already has its own course (VS Code Essentials) covering its extension ecosystem and workflow in depth. Android Studio has its own dedicated course too (Android Studio: The IDE Itself) — but for a different reason: that course isn't a general editor survey at all, it's specifically about Android development tooling, which happens to be built on a JetBrains foundation this course also touches, from a completely different angle.
What This Course Actually Covers
Three genuinely uncovered areas: nano, a minimal, always-available terminal editor; Sublime Text, a lightweight GUI editor sitting between a minimal tool and a full IDE; and the JetBrains family — IntelliJ IDEA, PyCharm, and WebStorm — sharing the same underlying platform Android Studio: The IDE Itself's own Chapter 1 already introduced, here covered from a general, non-Android angle.
A Spectrum, Not a Random List
These aren't an arbitrary grab-bag — they sit along one genuine spectrum of weight and capability: nano (minimal, instant startup, no plugin ecosystem) → Sublime Text (lightweight, fast, a real but modest plugin ecosystem) → the JetBrains family (full IDE, deep language-aware tooling, real startup and memory cost). Vim and VS Code sit at their own points along this identical spectrum too — this course simply doesn't re-teach them, since `vim1`/`vim2` and `code1` already do.
| Tool | Where it sits | Owned by |
|---|---|---|
| Vim | Minimal, modal, terminal-based | Learning Vim / Vim Intermediate/Advanced |
| nano | Minimal, non-modal, terminal-based | This course |
| Sublime Text | Lightweight GUI | This course |
| VS Code | Lightweight-to-mid GUI, huge extension ecosystem | VS Code Essentials |
| JetBrains family | Full IDE | This course (general) / Android Studio (Android-specific) |
Hands-On Exercises
A friend asks why this course doesn't cover Vim, since it's clearly a text editor. Explain the actual reason, using this chapter's own material.
📄 View solutionExplain why Android Studio: The IDE Itself isn't considered part of this course's own "JetBrains family" coverage, even though Android Studio is itself built on the IntelliJ Platform.
📄 View solutionA developer claims a full JetBrains IDE is "just strictly better" than nano in every situation, since it has vastly more features. Using this chapter's own warning box, explain what's wrong with this claim.
📄 View solutionChapter 1 Quick Reference
- This course skips Vim and VS Code (already owned by their own courses) and Android Studio (Android-specific, not a general editor survey)
- This course covers nano, Sublime Text, and the JetBrains family (IntelliJ IDEA, PyCharm, WebStorm)
- These sit on a genuine spectrum — minimal → lightweight → full IDE — not an arbitrary list
- The JetBrains chapters build directly on Android Studio: The IDE Itself's own Chapter 1 rather than re-deriving the shared platform
- More features is not automatically better — weight and complexity are real costs, matched against actual task needs in Chapter 8