After 14 months of running Deno 2.0 in production across 12 microservices, our 8-person backend team hit a wall: 62% of our weekly support tickets stemmed from package management edge cases. Migrating to Node.js 22 cut those issues by 40% in the first 30 days, with zero regressions in runtime performance. We didn’t just swap runtimes—we fixed a systemic friction point that was burning 18 engineering hours per week. 📡 Hacker News Top Stories Right Now Ghostty is leaving GitHub (1096 points) Before GitHub (61 points) OpenAI models coming to Amazon Bedrock: Interview with OpenAI and AWS CEOs (115 points) Warp is now Open-Source (164 points) Intel Arc Pro B70 Review (52 points) Key Insights Node.js 22’s native .env support and built-in test runner eliminated 3 third-party dependencies per service on average Deno 2.0’s npm registry compatibility layer added 210ms of cold start latency per function invocation in our AWS Lambda benchmark Reducing package management overhead saved our team $14,400 per quarter in…