Disclaimer: I've been an incredibly happy Arch user for two years now (have it on all my home systems) which may indicate my bias.
Whether I'm an "outcast" or a "neckbeard" is entirely for others to decide. What I can tell you is that based on your comment, you simply have never experienced the joy of building something from scratch.
Rather than defend Arch explicitly, I'd like to use an example.
I like bicycles. I cycle 20 miles daily on my work commute and use my bike as my only form of transportation for running errands and getting around town.
The most "usable" route of transitioning to a car-free lifestyle would have to be going to a bike shop and buying one that fits. Now of course there's nothing wrong with this approach.
However, using this approach, when something goes wrong (as inevitably will happen with all machines, mechanical or digital) my reaction would most likely be be to look down at the problem, scratch my head, then walk my ass to the bike shop.
The approach I prefer is to build my bike from scratch. Acquire the perfect frame, the ideal wheelset, a rack that saves me some extra grams over what comes default on most transpo bikes.
Then all the tools.
When something goes wrong with my bike, I know exactly what's wrong. I know what shortcuts I took, what configuration I chose, and most importantly, I've got all the tools necessary to fix the problem.
Further, I know my bike is as fast and efficient as possible (given all necessary trade offs) because I was able to choose the ideal components.
tl;dr: I use Arch because time spent tinkering is time spent learning and optimizing. For more info I suggest anyone interested read The Arch Way: https://wiki.archlinux.org/index.php/The_Arch_Way