Sur gcc et son steering committee: http://www.softpanorama.org/People/Stallman/history_of_gcc_d(...)
tout a la fin: The SC specifically avoids getting involved in technical issues whenever possible. Even when the SC is asked to decide something, they never go to RMS when they can help it, because he's so unaware of modern real-world technical issues and the bigger picture. It's far, far better to continue postponing a question than to ask it, when RMS is involved, because he will make a snap decision based on his own bizarre technical ideas, and then never change his mind in time for the new decision to be worth anything.
He can be convinced. Eventually. It took the SC over a year to explain and demonstrate that Java bytecode could not easily be used to subvert the GPL, therefore permitting GCJ to be checked in to the official repository was okay. I'm sure that someday we'll be using C++ in core code. Just not anytime soon.
Interest of other more flesh and motivated developers (as well as RMS personal qualities first demonstrated in Emacs/Emacs saga) led to a painful fork:
[^] # Re: Ça va les chevilles ?
Posté par thedude . En réponse à la dépêche Richard Stallman et la révolution du logiciel libre - Une biographie autorisée. Évalué à 10.
http://www.jwz.org/doc/lemacs.html
Sur gcc et son steering committee:
http://www.softpanorama.org/People/Stallman/history_of_gcc_d(...)
tout a la fin:
The SC specifically avoids getting involved in technical issues whenever possible. Even when the SC is asked to decide something, they never go to RMS when they can help it, because he's so unaware of modern real-world technical issues and the bigger picture. It's far, far better to continue postponing a question than to ask it, when RMS is involved, because he will make a snap decision based on his own bizarre technical ideas, and then never change his mind in time for the new decision to be worth anything.
He can be convinced. Eventually. It took the SC over a year to explain and demonstrate that Java bytecode could not easily be used to subvert the GPL, therefore permitting GCJ to be checked in to the official repository was okay. I'm sure that someday we'll be using C++ in core code. Just not anytime soon.
Interest of other more flesh and motivated developers (as well as RMS personal qualities first demonstrated in Emacs/Emacs saga) led to a painful fork:
Ya cette discussion sur slashdot aussi, interessant:
http://developers.slashdot.org/article.pl?sid=04/08/13/23562(...)
While a skilled and brilliant C and LISP hacker, RMS is a reactionary fuckhead when it comes to anything other than C or LISP.
Remember, in Free Software, you have the freedom to do anything you want -- except disagree with RMS.
Venant d'un mainteneur gcc.