I can totally sympathise with this - especially when if you look at the project's cargo.toml it looks simple enough, but turns out to have a boat load of transi

I can totally sympathise with this - especially when if you look at the project's cargo.toml it looks simple enough, but turns out to have a boat load of transitive dependencies as seems to be the case with that project. Plus the experience is somewhat exacerbated by Rust just generally being quite slow to compile. I think there's a mindset that is imported from agile business culture, more than anything else, that if you're not developing functional requirement business features as fast as humanly possible while meeting the bare minimum for quality then you're being slow and inefficient compared to the guy who's willing to do that. This same mindset also makes it completely unlikely that a tool with any kinds of barriers to entry which would have to be overcome on company time will ever gain any adoption. The other side of that coin is that where there are community projects which are not supported by companies where developers are just working in their spare time, often around work and so on, to develop something they think might be interesting but cannot commit to making everything the best it could possibly be while also realistically getting the thing done. It also has to work everywhere, it has to look pretty, it can't just work on whatever version of Windows is current and have done with it. Then there is just a logic to using dependencies because they've already been battle tested for you, there's a decent chance those developers have done a better job than you would given whatever limitations that you have simply because they've put the time and effort into it already. Maybe somebody's even paying them to do it.