Comment by andrewstuart
2 months ago
The problem Deno faces is that nodejs is “good enough”.
Pray you never have a “good enough” competitor.
I felt it should have aimed to be a 100% drop in replacement for nodejs then innovated on top of that.
2 months ago
The problem Deno faces is that nodejs is “good enough”.
Pray you never have a “good enough” competitor.
I felt it should have aimed to be a 100% drop in replacement for nodejs then innovated on top of that.
Tried moving a monorepo off Node once. The runtime swap was the easy part. What killed us was the 50-odd package.json files with node-specific stuff baked in. Conditional exports, postinstall scripts, engine constraints, pnpm overrides. Bun got this right by just eating all of that as-is. Deno asking you to throw out package.json on day one was basically asking you to rewrite your entire build config before you even got to try it.