Originally posted by theuserbl
View Post
Microsoft Continues "Demikernel" Development LibOS For Kernel-Bypass I/O
Collapse
X
-
Originally posted by Chewi View Post
Actually Microsoft use their own build of the regular Rust toolchain. When I last used it, it had some Cargo feature for fetching crates in a slightly different way. I don't know what other differences there are, if any.
The main Rust on the other side is currently in version 1.82.0 and publiched on October, 17.
So the version number of the Rust for Windows have nothing to do with the main Rust.
That reminds me a little bit to Microsofts Fork of the statistical language R called "R Open".
Microsoft R Open Source. Contribute to microsoft/microsoft-r-open development by creating an account on GitHub.
It was a fork of the main R.
Read-only mirror of R source code from https://svn.r-project.org/R/, updated hourly. See the build instructions on the wiki page. - wch/r-source
And R Open have had also its own version number, additional features and so on.
But R Open is currently dead. Last release for over four years ago.
Comment
-
-
Originally posted by theuserbl View Post
I was talking about Microsoft's Rust toolchain for Linux, which has broadly the same version number IIRC. I'd never heard of Rust for Windows.
Comment
-
-
Originally posted by varikonniemi View Post
Few people realize that good support for Linux is quite near in Redox land. With native or virtualized implementation. This is enough for most desktop use cases, only running AA or AAA games don't fit this paradigm.
Redox is nowhere near that yet. It can take a very long time indeed to implement compatibility with an existing moving target. See ReactOS.
I would hope that they'd get a fully working operating system up and running before attempting to make it compatible with another one.
Comment
-
-
Originally posted by NateHubbard View Post
Maybe, but I see that Redox is 9 (going on 10) years along already, and at that point Linux itself was a fully usable OS (I had been using full time at home and at work for quite some time by then).
Redox is nowhere near that yet. It can take a very long time indeed to implement compatibility with an existing moving target. See ReactOS.
I would hope that they'd get a fully working operating system up and running before attempting to make it compatible with another one.
Comment
-
Comment