Eric S. Raymond Calls Out The FSF/GCC On Clang
Eric S. Raymond has made some very interesting -- and what surely will be considered very controversial remarks -- about the Free Software Foundation's views on the GCC compiler and its lack of acceptance towards (potentially non-free) compiler plug-ins in a time of LLVM's Clang existence and ongoing acceptance.
ESR, the open-source programmer and free software advocate, wrote about clang and FSF's strategy on GCC's mailing list. In the mailing list post he quickly says, "Are the FSF's goals best served by continuing to technically restrict GCC? This is a question in which I have some positive stake. Yes, I continue to be opposed to the FSF's style of propaganda exactly because I think it hinders an end goal - a software ecosystem that is open-source and user-controlled - that I agree with and have worked hard to achieve. On the other hand, I have always said that the FSF's artifacts are its best artillery, and GCC is certainly one of the biggest guns in that arsenal. I want GCC to do what the FSF wants it to do - promote freedom and openness, erode proprietary control, prevent vendor lock-in of development toolchains. I think it is time to question whether the anti-plugins policy is still the best way to accomplish this."
Raymond went on to add, "What gives this question point is the very existence of clang. The clang developers aren't shy about saying in public that they regard the FSF's anti-plugin policy as obstructive and that this is a major motivation for their work. And they're making excellent progress; clang is a production-quality tool today, not yet as mature as GCC but with better features in some areas - its error messages, in particular are *far* superior."
Eric S. Raymond admits he believes that LLVM/Clang developers want to make GCC obsolete and says this BSD-like licensed compiler is a "credible threat" to GCC's dominance within the next three to five years.
Eric ultimately wants the Free Software Foundation to more happily welcome proprietary plug-ins within GCC. Eric wrote, "I point out that FSF can no longer prevent proprietary vendors from plugging into a free compiler to improve their tools. That horse has left the barn; the strategic goal of the anti-plugin policy has been definitively busted. I also think it bears noticing that nobody outside of Microsoft seems to particularly want to write proprietary compilers any more. GCC won its war; the cost and time-to-market advantages of hooking into open-source toolchains are now so widely understood that new processor designs support them as a matter of course. Wouldn't it make sense, then, to entirely drop the factoring restrictions from GCC so it can compete for developer attention more effectively with clang? Before clang existed, back when GCC had a near monopoly in its competitive space, there might have been a functional case for those restrictions. Reasonable people may differ on that; there's no point in arguing it retrospectively. Now, I submit, they have become a pointless gesture that serves only to hinder GCC development [and] increase clang's competitive advantage."
Eric ultimately ends with, "I urge the FSF to fully free the code - drop the policy restrictions, encourage a flourishing ecosystem of surrounding plugins. Let GCC, clang, and other alternatives compete for attention on pure technical merit. I think the last fifteen years have demonstrated that in this sort of competition, the proprietary vendors will eat dust if they try to outcompete open-source tools on their own ground. Furthermore, they've learned this the hard way, and are quite unlikely to try. There are less risky uses for their NRE. In some sense I don't really care who wins. Either GCC or clang will serve my needs. I do prefer that both tools be as excellent as possible. And it would be nice if the FSF were to demonstrate that it can recognize changed conditions and move with the times."
Read the rest of his mailing list post for more detail.
Latest Articles & Reviews
Latest Linux News
Most Viewed News This Week