The gcc error messages remind me of rms standing behind you yelling, "error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token (you idiot)!"
gcc error outputs are remnants of a bygone era where your brain contained the source of the compiler and the entire language specification. You are supposed to feel bad when you fail to please the parser (you wrote the entire compiler suite and implemented the language spec yourself after all, didn't you?).
Clang error messages softly whisper sweet nothings of suggestions and encouragement. You effortlessly resolve your typos and misconceptions. Before you know it, you're back into Productive Working Land having circumnavigated ancient realms of error messages from the past 20 years.
gcc error outputs are remnants of a bygone era where your brain contained the source of the compiler and the entire language specification. You are supposed to feel bad when you fail to please the parser (you wrote the entire compiler suite and implemented the language spec yourself after all, didn't you?).
Clang error messages softly whisper sweet nothings of suggestions and encouragement. You effortlessly resolve your typos and misconceptions. Before you know it, you're back into Productive Working Land having circumnavigated ancient realms of error messages from the past 20 years.