I wish Deno would keep doing what it does best
Summary
The article critique explores Deno's strengths in reducing configuration overhead and delivering built-in tooling, while arguing that the runtime is drifting toward Node.js compatibility. It narrates the author's personal journey from Python/Haskell to TypeScript within Deno, and analyzes how ecosystem decisions (npm compatibility, packaging, and dev-server gaps) influence a developer’s experience. The piece ends with mixed optimism, noting continued use of Deno while acknowledging trade-offs and uncertainties about future direction.