"rtfm" is definitely rude, and always has been. The f does not mean "fun". Besides, it is slightly ignorant, and if I may say so, it can be a bit neurodivergen

"rtfm" is definitely rude, and always has been. The f does not mean "fun". Besides, it is slightly ignorant, and if I may say so, it can be a bit neurodivergent. You see, manual pages are more often than not the wrong type of document to point people to. `man` pages are information-oriented. You can (or should, if they are well written, which is not always the case, but that's another matter) find all the information about a piece of software there - they are references. As you say, it's something that needs to be digested before you can use it. There's a certain kind of person, very commonly seen around computers, which can't help but digest a manual before they use a tool. Often they enjoy doing that. And that's fine. But that is not how everyone else does things. People often have a particular problem they want to solve. They want to know how to zip a whole folder, or generate a ssh key with a particular algorithm. Whatever. Something concrete. They want to solve that, they don't want to "digest a document in order to solve that". That is not something those people enjoy, or are good at. What those people need is a goal-oriented doc. Something that has a list of possible problems, and then gives solutions. Something that they can search for "whole directory" and find what they are looking for quickly. Something like a FAQ. This does not exist for all command lines (although the `tldr` app fits that well often enough for me). Blogposts are often (yet another) type of documentation, they are learning-oriented. Like a tutorial. The thing about blogposts is that they are indexed by Google, Bing and others. So in effect the combination of Google+Blogposts works like a big FAQ document. Please understand that I am not trying to be offensive here.