| |
| ▲ | swiftcoder 8 hours ago | parent | next [-] | | > in practice rust projects tend to have hundreds of deps That's really just any language with a built-in package manager. Go somewhat sidesteps this by making you vendor your dependencies, but very few other languages escape the ballooning dependency graph. | | |
| ▲ | phplovesong 7 hours ago | parent [-] | | Go has probably more packages than Rust, but i rarely see Go projects that use as many as rust. In Go the usuals are depending on the app, possibly some db drivers, a simple router and maybe some crypto related thing. Most projects do fine with just the stdlib. In rust i tend to see 100 deps, and 1000 transient deps. Compile times are not in seconds, but minutes. | | |
| ▲ | swiftcoder 5 hours ago | parent [-] | | You can do that just fine in Rust too, for example the Makepad[1] developers take a pretty extreme non-invented-here stance, and builds a full UI toolkit with no external dependencies (and a major focus on clean-build compile times). However, it isn't really part of the Rust OSS culture to operate like that. The culture typically values safety over compile times, and prefers to lean on a deep stable of battle-hardened abstractions. [1]: https://makepad.nl, https://github.com/makepad/makepad |
|
| |
| ▲ | the__alchemist 7 hours ago | parent | prev | next [-] | | This is a concern when viewing the Rust experience. It can be avoided by judiciously choosing dependencies that you need, and that have shallow trees of their own. I like to distinguish the rust lang from The rust OSS community. They overlap, but can be treated separately if you exercise case. | |
| ▲ | VerifiedReports 5 hours ago | parent | prev [-] | | "like we never seen"? |
|
