I fixed Windows native development (marler8997.github.io)

Article summary

The article discusses the difficulties of native development on Windows due to the complexity of the Visual Studio ecosystem. The author presents a solution called msvcup, a small CLI program that installs the MSVC toolchain and Windows SDK in a few minutes, allowing for versioned, isolated, and declarative dependencies. This approach aims to simplify the development process and make builds reproducible across machines. The author provides examples of using msvcup to build projects, including raylib, and highlights its benefits, such as fast installation and easy removal.

Main themes

• Windows native development
• Visual Studio ecosystem
• MSVC toolchain
• Build dependencies
• Development efficiency
• Cross-compilation

What commenters say

• The Visual Studio Build Tools can be installed without a license for open-source development, but there are limitations and constraints for commercial use.
• Some commenters argue that the LTSC channel is a viable alternative for stable and long-term support, but others point out its limitations and the need for a license.
• The use of msvcup is seen as a significant improvement for Windows development, allowing for faster and more efficient builds, but some commenters prefer alternative solutions like MingW64 or Clang.
• There is disagreement about the legitimacy and value of discounted Visual Studio licenses, with some seeing it as a scam and others considering it a legitimate option.
• Some commenters criticize the bloat and complexity of recent Visual Studio versions, preferring older versions or alternative development environments.
• The discussion highlights the complexity of Microsoft's licensing terms and the need for clarity on what is allowed and what is not, particularly for open-source and commercial development.