|
|
|
|
|
|
by alwaysdownvoted
3735 days ago
|
|
|
I still use SUA every day when I'm forced to use Windows. (I also run Linux binaries on BSD.) SUA is based on an old version of BSD, not GNU. tcsh, csh and sh. The compiler works. There is an old version of lex. For some of the userland, Windows binaries are provided, such as vi. It's better than nothing. Why did MS remove SUA from Windows 10? What harm would it do to remain an optional add-in as it was in Windows 7? Why do users have to upgrade to Windows 10 to use Linux binaries? Seems like Microsoft will do _anything_ to get users to upgrade. What are the privacy implications of Windows 10? Microsoft is very untrustworthy. Will users be able to run their own Linux binaries on Windows? Windows has never been a "pleasant experience". It's the unpleasantness of it that makes the alternative, UNIX, so appealing. |
|
|
... but is too outdated to be capable of bootstrapping clang. There's very probably a long chain of bootstraps that would achieve it, but there's not a direct route.
> Will users be able to run their own Linux binaries on Windows?
The answer to that is easily determined from the demo video that Microsoft published. In it, Russ Alexander compiles a program with (Ubuntu binary) GCC and and runs it.
Its implicit int in the declaration of main() was jarring. (-: