Sometime around 2000, busy people started complaining about this practice, and old timers started to hold their tongues. I knew the era was over when my Millennial co-worker one cube away asked me to not interrupt him and IM him instead, since he had to take off his earphones. About the same time, my boss complained about how long my (senior engineer, explaining matters related to the immanent demise of the company...) emails were -- frankly managers were busy and 1-2 sentence ought to explain about this O-ring problem.
Your projection of self-centeredness on the part of your elders is unbecoming and ill-informed. You are merely young.
rms is just old school.
I find most "short" messages lack key details, requiring me to either search out more information, request a clarification, or abandon the conversation (due to anticipation of the pain continued communication would cause). This is more time and mentally expensive to me than reading a longer more precise message.
Also RMS replies to a lot of the random emails he gets. Much more than a lot of people who are as well known as him to be fair.
Sounds to me like you are just not a big fan of RMS so find a negative in everything he does that isn't quite the norm.
For more on this, see: https://en.wikipedia.org/wiki/UUCP#Mail_routing
https://groups.google.com/a/mysociety.org/forum/#!msg/mysoci...
To people who think like rms, these rules are very helpful, but I think many people will get the impression that he is being very rude by having a long document with his preferences.
If you don't know what you're doing, you won't treat the other party seriously. This is a strong signal to the other party that you don't know what you're doing and SHOULD be avoided.
If -however- you do know what you're doing, then you take the other party seriously even when you come across such demands because (as shawn-furyan said):
> Those sort of riders are a sentinel to signal that the venue read the contract carefully... If they caught the brown M&M's thing, they probably got all the stuff about rigging safety, so you don't have to grill them on those things. Otherwise, you'd better double check.
http://ultimateclassicrock.com/david-lee-roth-van-halen-brow...
This applies to RMS -- when he's on the road, he's often at the mercy of the event organizer for transportation and lodging arrangements (either directly or indirectly by them providing information). If they mess up, he's in real trouble.
Never having met the guy, that doesn't really sound like rms' MO.
If he reaches to YOU, and he still demands that, then that's another story.
>The man certainly has some condescending opinions about software, but he is not conceited about his own celebrity - he quite certainly would gladly give it up if he could.
Which is why he's happy to let Linus get all the credit?…
I am not on vacation, but I am at the end of a long time delay. I am located somewhere on Earth, but as far as responding to email is concerned, I appear to be well outside the solar system.
After your message arrives at gnu.org, I will collect it in my next batch of incoming mail, some time within the following 24 hours. I will spend much of the following day reading that batch of mail and will come across your message at some point. If I write a response immediately, it will go out in the next outgoing batch--typically around 24 hours after I collected your message, but occasionally sooner or later than that. Please expect a minimum delay of between 24 and 48 hours in receiving a response to your mail to me.
If your message is hard to understand or responding takes real work, the response could take longer.
So please wait 48 hours after sending a message before you resend it, remind me about it, or ask if I have received it. If it has been less than 48 hours, the absence of a response from me only means you have not given me time to answer.
If you are having a conversation with me, please keep in mind that each message you receive from me is a response to the mail you sent 24 to 48 hours earlier, and when writing it, I probably had not yet downloaded your later mail.
If you are in big hurry to speak with me, and one day's delay would be a serious problem, you can ask my FSF assistant to phone me. Send mail to <[email protected]> saying what you would like to talk with me about, and giving your telephone number. You can also call the Free Software Foundation office at 617-542-5942 (weekday Boston business hours) and ask them to phone me on your behalf. If it's really important, try both!
An intermediate measure is to email me your phone number and ask me to phone you.
But if there isn't enough hurry to warrant phoning me, please don't bother the FSF people. The mail you already sent me will reach me before any mail they could send me now on your behalf. I will respond as soon as I can.
To contact the Free Software Foundation, use one of the addresses in https://www.fsf.org/about/contact/email.
If you do not wish to receive this message ever again, please send a message to [email protected] with the subject "OFF". Otherwise, you might receive a reply like this one up to once a month.