Re:Deno on MDN
by dmitriid on Tuesday August 24, 2021 @11:20AM
(#28290006)
> but usually that is true for npm packages as well
It's not true in a very, very, very big and important detail: once I found the packages, I do any of `npm/yarn/pnpm install package-name`, and it resolves the package, and all its dependencies
> Since each dependency is an url, it will fetch all deps and download them in order
How is each dependency a url when it's decidedly not? Or is deno silently re-writes all `package.json`s?
> You also don't need a package.json
Oh. Now you don't need a package json. So... How does Deno resolve dependencies for a package?
> I personally prefer to not be reliant on an american mega corporation which is known for it's anti-competitive practices and woke agenda.
Instead you rely on something that literally relies on megacorps for Rust, V8, Typescript.
> Well in that specific case you would need to download the entire tree and host it yourself.
Wow. So much convenience. I'm simply astounded. How is this a good thing again?
> I am convinced it's the future for server side javascript. It's just... nicer in general.
So far you've done literally nothing to show how it's nicer. For a developer it's a major pain in the butt: resolve dependencies manually, download them manually, grep+replace urls...
It's not true in a very, very, very big and important detail: once I found the packages, I do any of `npm/yarn/pnpm install package-name`, and it resolves the package, and all its dependencies
> Since each dependency is an url, it will fetch all deps and download them in order
How is each dependency a url when it's decidedly not? Or is deno silently re-writes all `package.json`s?
> You also don't need a package.json
Oh. Now you don't need a package json. So... How does Deno resolve dependencies for a package?
> I personally prefer to not be reliant on an american mega corporation which is known for it's anti-competitive practices and woke agenda.
Instead you rely on something that literally relies on megacorps for Rust, V8, Typescript.
> Well in that specific case you would need to download the entire tree and host it yourself.
Wow. So much convenience. I'm simply astounded. How is this a good thing again?
> I am convinced it's the future for server side javascript. It's just... nicer in general.
So far you've done literally nothing to show how it's nicer. For a developer it's a major pain in the butt: resolve dependencies manually, download them manually, grep+replace urls...
Edit: this comment by spankalee sums it up nicely: https://news.ycombinator.com/item?id=28276908