29 ms·
> It's why we get things like Deno, which attempt to throw all this cruft away and start again Doubt. Your "something@v1.2.3" in Deno is no different than "som
by rudian 5y ago
> It's why we get things like Deno, which attempt to throw all this cruft away and start again
Doubt. Your "something@v1.2.3" in Deno is no different than "something": "^1.2.3" in npm. The problems will appear when you update stuff.
The only thing benefiting deno currently is the clean slate and the lack of hacks (for now).
- Soremwar 5y agoThey are different, currently no Deno registries have dynamic version resolution (no greater than operator). Once you have locked in on a version you are in it for good unless you change it manually However if the argument is: updating libraries break stuff, that is gonna happen every time in every language. There is no guarantee the next version will just work as the last one did