Just use Deno

Short summary

A developer argues for switching from Node.js to Deno for new projects, citing Deno's built-in TypeScript support, formatter, linter, test runner, and security model as eliminating the ecosystem overhead of Node's config-heavy setup. The piece traces the author's journey from dismissing Deno in 2021 to adopting it after fatigue with Node's tooling complexity. Not AI-related but relevant to developer tooling decisions.

• •Deno eliminates config overhead: no tsconfig, no ESLint setup, built-in formatter/linter/test runner
• •Security model with explicit permission flags is a professional safeguard, not friction
• •Author switched after accumulating fatigue with Node's ecosystem complexity

Generated with AI, which can make mistakes.