Hacker News Reader

Correct me if I'm wrong, but this would mean that I will be informed about missing dependencies RUNTIME? And I have to do that multiple times, if there are multiple 'dynamic dependencies' like this. The main reason for having declarative dependencies is to NOT be having to do that.

View on HN

Yes, the missing dependencies would show up at runtime. Which is a valid and important concern, however: It would be possible (though probably inadvisable) to implement an automatic download of missing dependencies.

Which is as terrible idea. You have some code deployed, and suddenly this code downloads random things from internets without any control whatsoever.

Even worse if the application was deployed behind firewall and can't access internet freely.

It is definitely a bad idea when working on a server, but for a cli tool or some editor that might install it anyways it could be arguably worth a try.

It's JavaScript. If you make any thing that's merely silly in command line tools, it will end up being adopted where it's a terribly stupid idea.

Plugins are plugins and dependencies are dependencies. Don't mix them up.

Reply on news.ycombinator.com