Docker for windows is a thin shim over a VM that falls apart at the seams when it comes to networking..
Git on Windows is only supported by installing a whole suite of Unix tools and a shell.
Tools like ccache/sccache treat windows (well msvc) as a second class citizen.
Go, the poster child for cross-compilation shatters that illusion when you need to use CGO.
Python, I believe things have gotten better but the last time I tried getting tensorflow up and running on Windows it was a long and painful path involving third party python distributions, native toolchains and changing drivers.
Depends pretty much on the Windows version, and if using Linux or Windows containers.
Docker on Windows is a shim for the Windows Jobs API, as Microsoft decided to offer the same experience instead of coming up with their own set of tooling.
In more recent Windows versions, there are other ways to manage containers, specially after containerd support improved.
The best way to distribute builds on Windows is via incredible and their VS integration.
Cross compilation never really quite works out, unless one can have a complete set of libraries and toolset of the host OS, otherwise there will always be corner cases.
Python has been quite alright when using distributions like ActiveState Python.
Git, well one cannot expect better from a SCM designed for the Linux kernel project in first place.
Git on Windows is only supported by installing a whole suite of Unix tools and a shell.
Tools like ccache/sccache treat windows (well msvc) as a second class citizen.
Go, the poster child for cross-compilation shatters that illusion when you need to use CGO.
Python, I believe things have gotten better but the last time I tried getting tensorflow up and running on Windows it was a long and painful path involving third party python distributions, native toolchains and changing drivers.