I fixed Windows native development

Original Article ↗ Hacker News Discussion ↗

CI, local builds, and toolchain friction

  • Several commenters report huge productivity gains by avoiding Windows-based CI for native builds, instead building locally on a powerful desktop or extracting toolchains from CI images and reusing them.
  • Others argue the core issue isn’t where you build but that builds should be reproducible anywhere; CI should merely orchestrate, not own, the toolchain story.

Existing MSVC / Visual Studio solutions

  • Some say the problem is overstated: install “VS Build Tools” (optionally LTSC versions) via direct download, Chocolatey, or winget, then call cl from a simple script.
  • Teams report success with .vsconfig files and Visual Studio’s unattended installer / offline layouts, as well as official build-tools-in-a-container images.
  • There’s debate whether Microsoft’s side‑by‑side VS story really works; several report new VS versions breaking older installs, leading some to isolate each version in a VM.

Licensing and legality

  • Long back-and-forth over Visual Studio Build Tools licensing:
    • For closed‑source/commercial use, many read the terms as requiring a paid VS license.
    • For building (certain categories of) open source, Microsoft has relaxed requirements.
    • Some claim the tool in the article may violate terms if used for proprietary code without appropriate licenses; others say enforcement is lax or unclear.

Alternatives: MinGW, MSYS2, Clang, LLVM-MinGW

  • Strong disagreement over MinGW/MSYS2:
    • Fans like the lack of extra runtime DLLs and ability to target very old Windows.
    • Critics call MinGW “hacky,” ABI-incompatible with mainstream Windows libraries, and a bad signal for serious Windows support.
    • Nuanced takes distinguish MSYS2’s Unix-like dev shell (Cygwin-derived) from its native UCRT/MinGW environments.
  • Clang + MSVC headers/SDK, or LLVM-MinGW, are suggested as cleaner cross‑platform options, but still need Microsoft headers/libraries for full compatibility.

Native vs web and language toolchains

  • Some question whether native Windows apps are worth it at all given Electron/Tauri; others counter with performance, resource usage, games, and specialized native tooling.
  • Rust, Go, Zig, .NET, and Nix are mentioned as having better or at least different toolchain UX, yet many still hit MSVC dependencies (especially via FFI or Rust on Windows).

Reaction to the article and AI “slop”

  • Many praise the tool and idea; others think the article is over-dramatic or just re-wrapping an existing script.
  • Long subthread debates whether the writing style is LLM-generated or just mimicking now-common AI-esque listy prose, with visible fatigue over this meta-discussion itself.