3 ms·

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...