?? I build Jujutsu and many other Rust programs from source on Windows.
Rust has a much better Windows story than C and bash do, due to its heritage as a language built by Mozilla for Firefox.
?? I build Jujutsu and many other Rust programs from source on Windows.
Rust has a much better Windows story than C and bash do, due to its heritage as a language built by Mozilla for Firefox.
> Rust has a much better Windows story than C
This is an extremely strong statement. Which is so obviously factually incorrect that I tend to think you might have meant something else.
As a Windows user, I find random Rust projects work on Windows far more often than random C ones, even if the authors didn’t make a specific attempt to support Windows.
"work" as in "build"? I would agree with that.
And run.
My colleague Bryan Cantrill, famously a huge Unix guy, once said to me “if you had told me that projects I write would just work on Windows at the rate they do, I wouldn’t have believed you.” When I started at Oxide I had to submit like one or two patches to use Path instead of appending strings and that was it, for my (at the time) main work project.
I meant exactly what I said.
As said before I wasn't complaining about windows, but rather of not so common posix layers like cygwin [0]. Most C posix compliant stuff compiles in my experience.
[0] https://github.com/rust-lang/rust/issues/137819
Right, but Rust makes it so you don't have to use Cygwin. It's one of the great portability advantages of Rust that you can write real Windows programs with it.
I am not really sure if I can follow here. How could a rust compiled program like git honor my cygwin emulated mount points in paths, which I need, when working with other posix compliant software.
I thought that if you invoke a native Windows binary with Cygwin, it translates Unix-looking paths into Windows ones. But it's been a long time since I used Cygwin so I could be wrong.