That was addressed in the long (and interminable) example thread linked in the article. Because of RMS's opposition to making gcc usable in any context other t

That was addressed in the long (and interminable) example thread linked in the article. Because of RMS's opposition to making gcc usable in any context other than gcc, people just moved to llvm and clang. The core issue is that these are people who care about FSF, GNU, gcc, etc running headlong into RMS who is forcing design decisions based on a threat that does not exist, leading to the gradual erosion of there relevance. Take gcc as in the example thread: RMS intentionally hobbling gcc means that gcc is simply not involved in any significant amount of compiler and language research any more. Why bother? it's intentionally designed to make the kind of things that compiler researchers would want to do hard, to "stop it being used in non-free software", similar happens for new languages: why bother messing around gcc where by design your only real option is "compiling" your code to C, which comes with _many_ costs. These are people who _want_ to use gcc, who _want_ to use gpl, gnu, fsf, etc software, but cannot because functionally RMS does not allow it.