Deno 2.8 (deno.com)

Article summary

Deno 2.8 has been released, featuring several new subcommands, improved Node.js compatibility, and performance enhancements. The new subcommands include deno audit fix, deno bump-version, deno ci, deno pack, deno transpile, and deno why. Deno 2.8 also defaults to npm and supports the TC39 import defer proposal. The release improves Node.js compatibility, with a pass rate of 76.4% on Node's test suite, and includes various performance optimizations.

Main themes

• Deno 2.8 release
• Node.js compatibility
• Performance enhancements
• Package management
• JavaScript runtime
• Open-source sustainability

What commenters say

• The acquisition of Bun by Anthropic does not necessarily make it a safer bet as a dependency due to potential return-on-investment requirements.
• Deno's import mechanism and sandbox features are no longer unique selling points in the JavaScript runtime market.
• The JavaScript ecosystem has an abundance of options, but excessive fragmentation is a concern, and having alternatives like Deno and Bun can prevent stagnation.
• Being acquired by a big company can actually increase the risk of an open-source project being shut down or changed significantly for the worse.
• Node.js is still considered a stable and reliable option, and its compatibility with Deno is improving.
• The recent 'vibe code' incident has raised concerns about the reliability of Bun as a dependency.
• Public investment in open source through grants could be a more sustainable model than relying on corporate benefactors.
• The profitability of companies like Anthropic and OpenAI is not guaranteed, and their acquisitions may not ensure the long-term viability of projects like Bun.