Cross-compiling binaries for Windows is easier than building natively (gist.github.com)

Article summary

The article discusses the challenges of building software natively on Windows, with a focus on the issue of symbolic links (symlinks). Although NTFS supports symlinks, their use is limited by default due to security concerns. The article suggests that cross-compiling binaries for Windows may be easier than building natively. The discussion reveals that many projects use symlinks, and their limitations on Windows can cause issues.

Main themes

• Symlink support on Windows
• Cross-compiling vs native building
• Security concerns and mitigations
• Developer experience and workflow
• Platform compatibility and limitations

What commenters say

• Symlinks are not a major issue on Windows, as NTFS supports them, but their use is limited by default due to security concerns.
• The lack of symlink support on Windows is a significant problem for developers who need to use them.
• Windows developers should be aware of the existence and limitations of symlinks on their platform.
• The security concerns surrounding symlinks on Windows may be overstated, and alternative mitigations could be implemented.
• Enabling symlink support on Windows requires elevated permissions or developer mode, which can be a hurdle for some users.
• The limitations of symlinks on Windows are a result of the OS not being designed with wild symlinks in mind, rather than a technical limitation.
• Symlinks are a common feature in many projects, and their limitations on Windows can cause issues for developers who are not aware of them.