If you see something written like a snotty libertarian fossbro in the Archwiki and I know anything at all about the subject matter, I'll fix it if you point it out.

I'm beyond tired of docs written like "Any newbie should know the obvious solution to error 13 is to narfle your garthok. Narfling and garthoks are beyond the scope of this document"

@trysdyn

I hope that some day people will manage to take down the Arch Linux Install Guide techbro occupation >_>

@saphire Ugh. Yeah. Their insistence on not having an "easy" guide because "Easy means you're not making important choices!" is like... the No1 barrier to Arch itself.

Like I don't care what you think regarding choice and flexibility and openness, you need an easy option to see if this is even for you before you commit to learning about all these choices.

And haughtily going "That's other, less serious distros" doesn't endear anyone to your case.

@trysdyn My brief exploration so far into Arch, has given me the following idea of the Linux ecosystem:

Gentoo is the old, crotchety grandpa. He knows how to sharpen an axe and gut a deer.
Ubuntu is the well-meaning mother, who may be overbearing but is largely safe, you can trust her, and she'll make sure you get the food to your plate, without having to worry about how the sausage was made.
Ubuntu has many children, many different directions, some more popular than others, some more outrageous than others, but there's usually room for everyone at the table come holiday seasons.
Now we're at the great grandchildren of Gentoo. ArchLinux is the one who looks back and thinks, "Look at how cool that was! If they could compile their own kernel from source on a single core 1ghz processor, I can do way more now!" and so they do so, with all the smug arrogance that comes from someone who is doing it their own, instead of relying on all the modern QoL conveniences, and if you need your hand held you don't belong on the edge.
From Arch, we already have some children who realize how cringe being an elitist asshole is, and are building on what COULD be a solid foundation, but making it available to others.

@trysdyn at best this feels like Don't Repeat Yourself spilling out of coding and into realms where it doesn't belong. DRY can be good for code but in documentation it's just an excuse to be lazy 

I'm also reminded of high ranking Stackoverflow answers that say "this thread elsewhere solved my problem" only for that to have suffered linkrot (tearing my hair out)