3 ms·
I find the async stuff obnoxious, too, and I avoid it. Helps that I don't work in the web space. But in general the dependency story with Rust is better than w
by cmrdporcupine 3y ago
I find the async stuff obnoxious, too, and I avoid it. Helps that I don't work in the web space.
But in general the dependency story with Rust is better than with C++. I don't miss the integration story with C++; just bringing in a dep in the first place is a roll of the dice on whether it's going to work with your build system. And then whether it brings with it some other lifestyle assumptions (exceptions, some third party deps you don't want or can't link to, work with your compiler or not, etc.)
Honestly, I work in systems & embedded stuff, and it's not hard to avoid async in Rust. It's only once you start poking at web-adjacent stuff that you run into the wall, and then when you do you find yourself covered in the taint of people who brought their NodeJS Stockholm Syndrome over to Rust, but that's another rant...
- pjmlp 3y agoOr just stick with cmake + vcpkg/conan, and enjoy the existing ecosystem of C++ libraries. Nowadays it is impensable to do a Java project without Maven/Gradle, yet it took about 10 years for Ant to be relevant (counting from 1996), and couple more for Maven, and yet another few for Gradle. Similarly with NuGET and MSBuild evolution. Yet they were eventually adopted, same is happening with vcpkg/conan.