3 ms·
> Why do you treat adding a feature (npm compatibility) like you’re losing something? Because they are losing something. All the time and money they are inves
by pier25 1y ago
> Why do you treat adding a feature (npm compatibility) like you’re losing something?
Because they are losing something.
All the time and money they are investing into node compat could have been used towards a Deno first party ecosystem. It's not like they have hundreds millions to spare. Deno is a small company with limited resources.
People kept complaining that they couldn't use Deno with NPM packages so Deno ended up focusing in providing faster horses.
- hombre_fatal 1y agoI think the upsides of Deno having its own isolated ecosystem are way overstated. In practice, it would stay a small group of hobbyists responsible for doing weird things like maintaining ports of npm libraries that deno users want, like official SDKs. It’s a grim end state if you’re trying to be more than that. And it seems to only appeal to people with a weird vendetta against Node/NPM which is also a crappy user to cater to.
- pier25 1y agoI'm not saying Deno should leave the ecosystem up to "a small group of hobbyists". What I'm arguing is that Deno investing in an official ecosystem would have been a better early investment than Node compat.