3 ms·

As I said on the other post, I strongly doubt that. It offers few benefits and many roadblocks. It would be a monstrous amount of work, would throw into questio

As I said on the other post, I strongly doubt that. It offers few benefits and many roadblocks. It would be a monstrous amount of work, would throw into question many existing security-related certifications, break Microsoft's love of backwards-compatibility, etc. All MS is trying to do is make it easier for developers to develop on Windows for Windows, which it has ample incentive to do both internally and externally.

0cf8612b2e1e 3y ago
I have been continually disappointed that Microsoft has not released a seamless Windows virtualization system. WindowsX would run the new, redesigned APIs, but all of the legacy could run inside a sandboxed system to give the world the required decades to finally transition.
- doubled112 3y ago
  Windows Subsystem for Windows?
  - __egb__ 3y ago
    How about, “Winception”
  - yrro 3y ago
    Already exists, read up about "Windows on Windows" and "WOW64" :)
  - al_borland 3y ago
    It’s basically what Apple did when moving from OS 9 to OS X. Old applications would load up in Classic, allowing users to start using the new system, while developers had time to update their apps.
- mrj 3y ago
  This! I won't buy a Windows OS to run stuff because rebooting is annoying and I end up rarely ever actually dual booting. But I'd pay good money for a Windows Classic library on Linux.
  - mrj 3y ago
    Imagine if they could sell a copy of Windows for each legacy app or game you want to run, instead of the one copy running the hardware...
- int_19h 3y ago
  There have been experiments along these lines for some time now. E.g. there's https://learn.microsoft.com/en-us/windows/security/application-security/application-isolation/windows-sandbox/windows-sandbox-overview https://learn.microsoft.com/en-us/windows/security/applicati... And before that, some people might remember https://en.wikipedia.org/wiki/Virtual_PC#Windows_XP_Mode https://en.wikipedia.org/wiki/Virtual_PC#Windows_XP_Mode.
calamari4065 3y ago
I'm really amused that the least painful way to develop for Windows on Windows is to just use Linux.
- delta_p_delta_x 3y ago
  > the least painful way to develop for Windows on Windows is to just use Linux Eh? Even as a joke, I don't get it. 1. Download Visual Studio 2022 Community Edition 2. Select and install the workloads you need 3. Fire up any boilerplate from the Welcome menu 4. Press the green play button Sure, it's no `pacman -S base-devel && g++ main.cpp && ./a.out`, but it's not as bad as everyone puts it. It is a GUI-first operating system, and if you want to write a fast, HiDPI-aware Win32 application today that supports everything from Windows XP to Windows 11 that's < 50 kB, you absolutely can.
  - calamari4065 3y ago
    Replying to > All MS is trying to do [with WSL] is make it easier for developers to develop on Windows for Windows, which it has ample incentive to do both internally and externally. > if you want to write a fast, HiDPI-aware Win32 application today that supports everything from Windows XP to Windows 11 that's < 50 kB, you absolutely can. I said "least painful", not impossible. The scenario you describe here would be very painful.
    - delta_p_delta_x 3y ago
      > The scenario you describe here would be very painful On the contrary, it couldn't be easier. Visual Studio comes with a Windows XP platform toolset[1] that is a one-click install. Compare, on the other hand, how ridiculously hard it is to develop targeting older glibc on a newer glibc host. There's no way around it except to use a Docker container (which IMO is equivalent to using a sledgehammer on a tiny nail). [1]: https://learn.microsoft.com/en-us/cpp/build/configuring-programs-for-windows-xp?view=msvc-170 https://learn.microsoft.com/en-us/cpp/build/configuring-prog...
lvass 3y ago
>Microsoft's love of backwards-compatibility This is like, the primary reason to do this move. Wine has better compatibility for windows software than windows has now in my experience.
- int_19h 3y ago
  It's far easier to port Wine to run on modern Windows than to port Windows to run on a Linux kernel.
  - delta_p_delta_x 3y ago
    It's also far easier to port an old Windows application to run on modern Windows, or write a program on modern Windows targeting old Windows, than it is to do any of this on Linux.

0cf8612b2e1e 3y ago

I have been continually disappointed that Microsoft has not released a seamless Windows virtualization system. WindowsX would run the new, redesigned APIs, but all of the legacy could run inside a sandboxed system to give the world the required decades to finally transition.

doubled112 3y ago
Windows Subsystem for Windows?
- __egb__ 3y ago
  How about, “Winception”
- yrro 3y ago
  Already exists, read up about "Windows on Windows" and "WOW64" :)
- al_borland 3y ago
  It’s basically what Apple did when moving from OS 9 to OS X. Old applications would load up in Classic, allowing users to start using the new system, while developers had time to update their apps.
mrj 3y ago
This! I won't buy a Windows OS to run stuff because rebooting is annoying and I end up rarely ever actually dual booting. But I'd pay good money for a Windows Classic library on Linux.
- mrj 3y ago
  Imagine if they could sell a copy of Windows for each legacy app or game you want to run, instead of the one copy running the hardware...
int_19h 3y ago
There have been experiments along these lines for some time now. E.g. there's https://learn.microsoft.com/en-us/windows/security/application-security/application-isolation/windows-sandbox/windows-sandbox-overview https://learn.microsoft.com/en-us/windows/security/applicati... And before that, some people might remember https://en.wikipedia.org/wiki/Virtual_PC#Windows_XP_Mode https://en.wikipedia.org/wiki/Virtual_PC#Windows_XP_Mode.

calamari4065 3y ago

I'm really amused that the least painful way to develop for Windows on Windows is to just use Linux.

delta_p_delta_x 3y ago
> the least painful way to develop for Windows on Windows is to just use Linux Eh? Even as a joke, I don't get it. 1. Download Visual Studio 2022 Community Edition 2. Select and install the workloads you need 3. Fire up any boilerplate from the Welcome menu 4. Press the green play button Sure, it's no `pacman -S base-devel && g++ main.cpp && ./a.out`, but it's not as bad as everyone puts it. It is a GUI-first operating system, and if you want to write a fast, HiDPI-aware Win32 application today that supports everything from Windows XP to Windows 11 that's < 50 kB, you absolutely can.
- calamari4065 3y ago
  Replying to > All MS is trying to do [with WSL] is make it easier for developers to develop on Windows for Windows, which it has ample incentive to do both internally and externally. > if you want to write a fast, HiDPI-aware Win32 application today that supports everything from Windows XP to Windows 11 that's < 50 kB, you absolutely can. I said "least painful", not impossible. The scenario you describe here would be very painful.
  - delta_p_delta_x 3y ago
    > The scenario you describe here would be very painful On the contrary, it couldn't be easier. Visual Studio comes with a Windows XP platform toolset[1] that is a one-click install. Compare, on the other hand, how ridiculously hard it is to develop targeting older glibc on a newer glibc host. There's no way around it except to use a Docker container (which IMO is equivalent to using a sledgehammer on a tiny nail). [1]: https://learn.microsoft.com/en-us/cpp/build/configuring-programs-for-windows-xp?view=msvc-170 https://learn.microsoft.com/en-us/cpp/build/configuring-prog...

lvass 3y ago

>Microsoft's love of backwards-compatibility This is like, the primary reason to do this move. Wine has better compatibility for windows software than windows has now in my experience.

int_19h 3y ago
It's far easier to port Wine to run on modern Windows than to port Windows to run on a Linux kernel.
- delta_p_delta_x 3y ago
  It's also far easier to port an old Windows application to run on modern Windows, or write a program on modern Windows targeting old Windows, than it is to do any of this on Linux.