2 ms·
When Cargo removed POSIX-only features (running a bash script pre-build), I protested. Who cares about Windows and their mess!? But in retrospect that has been
by pornel 6y ago
When Cargo removed POSIX-only features (running a bash script pre-build), I protested. Who cares about Windows and their mess!?
But in retrospect that has been a great decision. The ecosystem has followed and supports Windows without friction. Cargo solves the "pile of unpacked library directories" problem. Crates that use system dependencies know how to use vcpkg or build from source. They will even read Windows registry for you to configure MSVC, so you don't need to run vcvars.bat.
The effect is that I can just write stuff on Mac, and my Rust projects mostly "just work" on Windows.
- Measter 6y agoI develop on Windows, and my experience has been that unless a crate is specifically written for another platform, they generally work perfectly fine on Windows with two exceptions: 1. Terminal-related functions. This is getting better as cross-platform libraries are made, but Windows has had a generally shite terminal emulator and the more common libraries expected a *nix-style terminal. 2. The crate has a C or C++ dependency.
- int_19h 6y agoThe terminal story should be a lot better on Win10 these days, what with ConPTY and VT100 support.