title: MSVC or MinGW for distributing close-source C++ executables for Windows?
body: <p>I've heard that 98% of companies use MSVC when distributing closed-source binaries for Windows.
  <br />
  The management of my company doesn't like the idea of paying Microsoft for compiling our own C++ software, so we use MinGW and distribute the 64-bit executables as-is, no installers either.
  <br />
  We statically link to MinGW runtime libraries.
  On Linux we also distribute raw binaries that we compile on Ubuntu 16.04.7 and dynamically link to glibc and glibcxx.
  <br />
  Everything seems to just somehow work.
  Are there any pitfalls that we might encounter, or other reasons why we should be doing what everyone else seems to be doing, which is to compile with MSVC and use Inno Setup? It there anything wrong with doing things simple?</p>