Ok so Arch apparently has an install script that does everything[0]. I tried it the other day and it's pretty flawless, albeit terminal-based so not for everyone I guess.

Pacman is _amazing_. Apt broke dependencies for me every few months & a major version Ubuntu upgrade was always a reformat. Plus, obviously, the Arch wiki is something else. I would go as far as to say you'll have an overall better Linux experience on Arch than Ubuntu and friends, even as a beginner.

[0]: https://wiki.archlinux.org/title/Archinstall

Everyone says this but I have only ever used arch. Wiped windows and started with Manjaro. No VM to test straight to bare metal. I learned how Linux worked and then installed the base arch distro. If you can read a wiki, you can use arch. It's not rocket science. All the available arch flavored distros make it even easier today. I tried debian once and found it even more cumbersome. Is it apt or apt-get? is it install or update? Never stuck around to find out.

Or ... like me, switch to Fedora full time 20 years ago and still use it (ok, I use AlmaLinux on my workstation and servers)...

I started with Slackware Linux—something arguably even more “hard-core” than Arch.

What mattered most at the beginning was good installation documentation, and both Arch and Slackware delivered on that front. Slackware, however, had an additional appeal: it was intentionally simple, largely because it was created and maintained by a single person at the time. That simplicity made it feel conceivable that the system could be fundamentally understood by a single human mind.

Whether a newcomer appreciates the Slackware/Arch approach depends heavily on learning style and goals. You can click through a GUI installer and end up with a working distro, but then what? From a beginner’s perspective, you’ve just installed something somehow—and it looks like a crippled Windows machine with fewer buttons.

Starting with Slackware gave me a completely different starting reference point. Installing the system piece by piece was genuinely exciting, because every step involved learning what each component was and how it fit into the whole. The realization that Linux is essentially a set of Lego bricks—and that I might actually master the entire structure, or even build my own pieces—was deeply motivating.

That mindset was strongly shaped by how Slackware and similar distros present themselves. Even the lack of automatic dependency management acted as an early nudge toward thinking seriously about complexity, trade-offs, and minimalism, which stayed with me forever.