I think Arch wiki provides recipes and howto's not documentation.

Common reason why some probably won't use Slackware: "Muh package management and muh dependency checking."

2 members found this post helpful.

Oh, right, so that must be why at the top of the main page of the Arch wiki you find the following: "Welcome to the ArchWiki: your source for Arch Linux documentation on the web." Lol.

Yes. When you're starting out with Slackware it requires dedication and effort to read the documentation to set-up your Slackware system.
Once a Slackware-stable system is set-up I don't think it requires constant effort to maintain it. If you want to continue to grow in your understanding of Slackware that requires effort.

4 members found this post helpful.

I don't understand what is your point. I didn't ask questions in this thread. What do you mean with my question is in line with why did you stop using Mandrake, CRUX and other from your list? If you are provoking then you are wasting your time, I don't care nor want to argue on forums. If we cannot have a civil exchange and learn from each other I will just ignore your posts.

I used those distributions for couple of months tops. Slackware has been my distro for years.

There is nothing difficult in tweaking a distro. Of course in Slackware is easier but that doesn't mean you cannot do it in others. All you need to do is read the documentation and ask questions to people who know more than you do.

I am not responsible what actually people from Arch put on top of their web page. Just go and look for real documentation: say old X server has eleven books of documentation each of which is hundreds of pages. Read documentation for POSIX standards. I think that people from Arch they just address their recipes all together as documentation - but it is more or less cookbook.

It depends on what you define as effort. I think it takes effort to keep with updates of the additional packages. If your needs never change and you add only a couple of packages then of course you are right. There is nothing else to do.

Best case is when you don't need anything else besides the official repo. Then there is really no more effort to put in it. In this case I absolutely agree.

Okay, whatever, call it a cookbook if that makes you happy. In any case, I disagree with your comment that "More detailed documentation just causes even more confusion," but maybe that's how it seems to you. Maybe you don't get anything out of man pages, either, I don't know.

Yes, effort is required but it is not a show-stopper for me. I am not educated in computers and am 67 years old. My laptop has Slackware64 14.2 installed as well as about 280 programs. Most of these are from SBO but some are Alien Bob's including KDE Plasma 5. My system is up to date at all times without breaking a sweat

You have just started the other thread never giving us explanation what is the reason. Now I think there is no reason. Maybe I am wrong but it looks like you are just jumping from distro to distro. So for me your thread seems to be provocative asking people for reasons in situation you yourself didn't have reason at all to stop using Slackware. You are just jumper. It's all your reason leaving distributions.

Sorry if I disturbed you. Just put this on my poor knowledge of English. I am Polish it is not possible to me to realize all the context of I am saying.

I hope you will go back soon.
I don't think many people are thinking the same. Maybe now you are the one who "knows more" than others?

Code
it reports 3375 lines.

I have stated my motivation in that thread. I think you missed my post, and my intention was not to provoke there nor here.

The only distros I used more that two months are Slackware, Arch and Ubuntu. I am already back so you don't need to hope.

English is not my mother language either but your hostility is clear here.

Now we better stay in topic.

Yes folks, please stay on topic.

You have all my respect for the dedication.

ArchArael, thanks for following up, alot of OP's become MIA with follow ups