Challenge 2: "No Plugins or Completion Means Inferior" — Solution Walkthrough

Why this misses the point:

Per this chapter's own material, the absence of a plugin ecosystem,
code completion, and a project concept is a deliberate scope
boundary in nano's own design, not a missing feature nano failed to
implement. nano is built around editing exactly one file at a time,
quickly, with zero setup — none of those omitted capabilities are
things nano is trying and failing to offer; they're outside what
nano was ever designed to do in the first place.

Why "inferior" is the wrong framing:

Judging nano against a full IDE's own feature checklist treats every
editor as if it's competing on the same axis — maximum features. Per
Chapter 1's own spectrum framing, nano occupies a genuinely different
position on that spectrum entirely, optimized for near-instant
startup and zero learning curve rather than deep language-aware
tooling. Comparing it unfavorably to a full IDE on feature count alone
ignores that the two tools are solving different problems.

The more accurate comparison:

nano should be judged on how well it serves its own actual purpose —
a fast, always-available, single-file editor — not on how many
IDE-style features it lacks, the same way a full IDE shouldn't be
judged on how slow it is to open for a 10-second edit.

WHY THIS WORKS AS AN ANSWER
------------------------------
This exercise directly applies this chapter's own "deliberate scope
boundary, not a missing feature" point to a realistic dismissive
comment, correctly reframing the comparison around fitness for
purpose rather than raw feature count.