4 ms·
> I don't like package.json either I think you're seeing it from the wrong perspective. I, as an ardent NodeJS user (hooray UI development), think NodeJS has
by nawgz 4y ago
> I don't like package.json either
I think you're seeing it from the wrong perspective.
I, as an ardent NodeJS user (hooray UI development), think NodeJS has a lot of problems. Less now, but a lot. Any list of pros and cons for NodeJs looks a bit like this:
Pros:
* Package management
Cons:
* JavaScript
The fact that the deno guys were like "yeah, this whole NodeJS thing sucks, let's throw it all out", only to never have an answer for easy package management, looks incredibly foolish from my perspective. NodeJS might be the single best language for package management today.
I agree with the point that adding support for it is pragmatic, but I am asking the question: how was such a pragmatic thing thrown out in the first place for "principled" reasons? Those principles look very foolish to me, both then and especially now.
- petre 4y agoThe problem is that npm package management is so stupidly easy that it creates other problems like dependency creep and supply chain attacks. Perhaps the Deno team wanted to do away with this but could not or maybe bother with it later on.