4 ms·
I was put off by Deno because of the way it handles dependencies. I didn't understand why I had to use URLs instead of `npm i`. Also not a big fan of the permis
by alabhyajindal 2y ago
I was put off by Deno because of the way it handles dependencies. I didn't understand why I had to use URLs instead of `npm i`. Also not a big fan of the permissions flags when running a command. Explicit declaration for every single permission was very annoying.
Bun has better speed and great documentation. And they're shipping new features very fast.
- tracker1 2y agoYeah, I think import maps resolves a lot of those issues myself... I both loved and hated it. I liked that it was just a matter of referencing any live source module, but hated trying to keep various references synced (like std).
- jeswin 2y ago> I didn't understand why I had to use URLs instead of `npm i` (a) With npm, Microsoft is the gatekeeper of everything NodeJS. URLs are the most decentralized way to do dependencies. (b) Self-hosting can help with some security issues with npm. Makes it easier for private projects to not have to trust npm hosted third party libraries, which is important in many corporate environments.