It continues to be disappointing (which I think is the least strong word that could be used) that clang's website attempts to demonstrate the superiority of clang by comparing against the error messages from gcc 4.2, a version of gcc that wasn't even the most current when that comparison was published. This then leads to people accepting this as fact (especially amongst developers targeting Apple products who don't even seem to realize versions of gcc later than 4.2 exist, as Apple refused to continue work on gcc due to the licensing changes) an turn up in answers like this one as the "most notable" technical advantage of the product.

In fact, the error messages of the two systems are largely a tradeoff at this point, and in a project I work on that compiles using both gcc and clang (targeting MinGW and OSX) simultaneously, on multiple occasions gcc has returned the more useful error messages (even if you discount the times when clang outright crashes while trying to compile my code, something gcc hasn't done to me in a decade). Even to the extent to which clang is better (which is mostly how it will guess what you meant and then compile the rest of the file under that assumption), it is kind of insulting in an open source context to treat that as a competitive advantage when I'm certain gcc would have loved that patch as a contribution.