I put unix in quotes ("for this" referring to interop). Was responding to someone who said "interop with Unix"
2: infrastructure pieces that already support Windows", which imo is a big part of why it feels harder. I also have done a ton of interop
-
-
3: work, including doing the design for the Rust time stdlib and helping with the Rust nix (Unix shim) and mio libraries in the early days
-
4/4: I this it's unquestionable that the experience of supporting Windows is harder. The question to ask is why.
-
What's the ideal way to distribute a C library to make it easy for Windows developers to use it? Bare .c & .h files to copy paste?
-
It would literally be a one-liner in Rust so there's no need for it ;) targeting software that can't yet integrate Rust into their toolchain
-
(Which btw if you want to talk about OS distribution is basically "everything that targets any Linux or BSD" but that's another rant)
-
.c and .h is a good enough packaging then, yes.
-
Are you just saying Rust can't target FreeBSD?
- 17 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.