| > For the record, I also disagree with your assertion that "easily done in rust" should be extended to include "...by importing a third-party framework." In that sense anything is easy to do in any language where a third-party framework exists. I'm confident it's just as easy in go. Have you tried doing that in C++? Doing that in a cross-platform way (or even in a single platform) is anything but easy, because you don't have a tool like cargo, you have to change your build system, do the dependency resolution manually, etc. So no, such a library existing does not imply that using that is easy. In Rust, you just need to write `cargo add unicode-segmentation` once in a project, and then you can directly use the library API. There is literally nothing else for you to do. That's a pretty low barrier of entry, and something you will need to do 100s of times per project anyway, because the standard library is minimal by design. If you prefer languages without a minimal standard library, then Rust isn't for you. Go try Python, where half of the standard library has a warning saying "deprecated: use this other better external dependency instead; adding this to the standard library for convenience was the worst idea ever and now we need to maintain all this code forever". |
In C++ I can write `vcpkg install whatever`. Yet that does not mean my organization will allow the library.
So no, adding libraries is quite harder than installing them unless you are working in your own projects alone. And even then adding them is never a one line effort.
> If you prefer languages without a minimal standard library, then Rust isn't for you.
There is nothing minimal about Rust's std.