Fool! You are never done!

@JP If you know what you are doing, arch is your best friend, and you can get all of the new cutting edge stuff without manually installing it. If you don’t know what you are doing, dual boot in cqase you brick something.

I feel you, however you only have to install arch successfully once per CPU archetecture, after that you can simply duplicate your install onto an infinite number of machines without having to re-install

Mac: Hello, I’m a Mac.  
Windows: And I’m a PC.  
Linux: I’m a PC too!  
Mac and Windows laugh their asses off.

@JP  
Surely you’re exaggerating? I’ve been using Arch for 3 years and it went into unbootable state twice (one time was because of my mistake). And you can downgrade - either by not deleting everything from /var/cache/pacman/pkg immediately after upgrade like an idiot (which is actually the reason why the cache doesn’t purge automagically - they warned about it in the wiki) or using makepkg on official PKGBUILDs from ABS archives. Hardly rocket science.
 
Though it is kinda frustrating how the devs build everything with libpulse compiled in (or listing it as dependency even when the lib is clearly not linked, forcing me to create a dummy package just to keep myself from frothing in my mouth) and started forcing everypony to use systemd by dropping support for rc.d (even though it would be easy to maintain both init systems).
 
By the way, systemd is a useless piece of garbage that should never have become reality, just like ALSA.

@gallagher117  
Everyone who considers using Arch needs to ask themselves one question:
 
Do I need this computer for actual work?
 
If the answer is yes, then avoid Arch. Otherwise, go ahead. You will get it into a state where it works for a while, but it will break. You have to update it every day. There are no stable releases; it’s more like if Canonical released a new Ubuntu every day and the new version might not work at all. If it doesn’t work, too bad, you can’t go back to the previous version. You can’t even reinstall it to go back, because reinstallation updates everything to the newest version. If the update breaks you system, well, you should not have updated it. Didn’t you read the news?

Is arch that bad? I’ve tried gentoo (stage3) in a VM. It taught me a lot. Like how JFS isn’t very resistant to corruption on crashing. But yeah, the theme of that install was “customize EVERYTHING”. View all the kernel build options (ALL of them). Use like 5 different partitions, each with a different FS (ext4, XFS, JFS, etc.). God, I wasted all day on that. Almost got a GUI installed, too.

@Psychopomf  
I’m not big on op systems for computers (wasn’t really interested in it) but to a gear head (like myself) a giant box of car parts and a fully loaded tool box just to build the car would be heaven to me (with instructions)

I remember someone once describing Linux
 
It’s like you buy a really fast and fuel effecient car. And then you get a knock on your door. And there is a giant crate full of car parts and a fully loaded tool box for you to build it yourself.

I used to run Arch for two years. Last year they broke it TWICE. Completely broken, won’t boot anymore. Then I realized my life is too short to micromanage an operating system. Yes, it is tiny and nice, but the maintainers have an obsession to break everything just because. If you don’t read the news section on the front page every day, your setup will break on the next update because you’re “doing it wrong”. Well, it will break anyway. Got <feature X> working? Good for you, we’ll break it next week by changing something for no reason.
 
And don’t get me started on the braindead setup process. The package signing was bad enough.

You’re never done installing Arch.