4 ms·

With all due respect, 166 packages to compile for a 5 line hello-word is so Nodejsy. It is a smell, a red flag. We should learn more from Go and Erlang. I hope

• jake_the_third 8y ago
  >166 Yikes! Does anyone know where I can get an overview of the entirety of rocket's dependency graph. Crates.io only lists 11 direct dependencies.
  • IshKebab 8y ago
    No, but that would be a good project. Probably the easiest way at the moment is to see the compilation output. E.g. from the CI logs: https://travis-ci.org/SergioBenitez/Rocket/jobs/465537062 https://travis-ci.org/SergioBenitez/Rocket/jobs/465537062
  • TimNN 8y ago
    You can use the `cargo graph` [0] command to get a graphviz view of the dependency graph. The `Cargo.lock` file which Cargo generates should also contain all the information you want in machine-readable form. [0]: https://github.com/kbknapp/cargo-graph https://github.com/kbknapp/cargo-graph
• steveklabnik 8y ago
  Tide is pretty expressly being built as a collection of smaller packages; I would expect it to have far more than Rocket.
• IshKebab 8y ago
  I do agree, and Go is definitely better in this regard, but why is that the case? I can't see any technical reasons for it.
  • deleted 8y ago
    [deleted]
• ordu 8y ago
  If you try to compile hello-world in C, you would need a gigantic libc.so, with a lot of stuff you do not need. These 166 packages you need to compile Rocket, not your hello-world. Rocket itself is much more complex then your hello-world, like libc.so is much more complex than hello-world coded in C, I see nothing wrong with it. Rocket and libc.so were created for solving a wide class of problems and hello-world is just one problem from that class.