Re:When an implementation monoculture might be the right thing
by asfasgasg on Thursday May 31, 2018 @10:49PM
(#17202222)
It's been a minute since Borland or Watcom were mainstream C compilers on Windows. Consider the year between ~2000-2015. Based on my recollection, it seems like MSVC was used at least 75% of the time, with the other compilers each having a small slice of the remaining quarter. Today, very seldom do you encounter a program that was compiled with anything other than MSVC, although with Clang that's starting to change.
I don't know too much about the history of Mac compilers. You may be right.
Back in the days, it was easier to make a competitive C compiler, because the accretion of advantages to the dominant compilers was not so large. Today, the moat is too wide and too deep. There's also no reason to build a new compiler, because nobody is going to pay you for it unless it's substantially better than the free ones, which by this point are pretty damn good.
Re:When an implementation monoculture might be the right thing
by JdeBP on Friday June 01, 2018 @06:06AM
(#17203978)
The existence of Clang (ironically the very compiler discussed in the headlined article) undermines your argument, based as it is upon there being "no reason to build a new compiler".
Re:When an implementation monoculture might be the right thing
by sanxiyn on Friday June 01, 2018 @12:01AM
(#17202475)
I use many programs compiled with GCC on Windows. MinGW works.
Re:When an implementation monoculture might be the right thing
by asfasgasg on Friday June 01, 2018 @12:08AM
(#17202500)
I'm sure you can find someone who uses many programs compiled with TCC. That tells me little about the actual prevalence of programs compiled using various compilers.
Re:When an implementation monoculture might be the right thing
by sanxiyn on Friday June 01, 2018 @12:24AM
(#17202542)
I believe NumPy Windows binary is built with MinGW. NumPy is used enough that it is more than "very seldom".
Re:When an implementation monoculture might be the right thing
by filmor on Friday June 01, 2018 @01:34AM
(#17202830)
Python C extensions are (supposed to be) compiled with the same compiler as the Python interpreter you are building against was, which in case of the official python.org release is MSVC, see https://wiki.python.org/moin/WindowsCompilers.
Re:When an implementation monoculture might be the right thing
by tavert on Monday June 04, 2018 @08:01PM
(#17233804)
And that choice of compiler has caused endless headaches for the NumPy and SciPy communities, see e.g. https://github.com/numpy/numpy/wiki/Numerical-software-on-Wi... and https://mingwpy.github.io/motivation.html
VLC's windows binaries are also built with mingw-w64 gcc last I checked, that is likely used even more widely than numpy.
Re:When an implementation monoculture might be the right thing
by justincormack on Friday June 01, 2018 @03:45AM
(#17203379)
Go and CGo both require gcc on Windows.
I don't think this is even remotely true.
On Windows in the 90's we had Borland, Watcom, Microsoft compilers. Today there is at least MSVC and icc.
On Mac there was Think C, Metrowerks Code Warrior, and others.
For embedded systems there are multiple commercial compiler vendors, as well as the open source tools.