It’s because it’s bleeding edge, extremely well documented and extremely popular. Bleeding edge is exciting and you’re gonna end up on the arch wiki anyway regardless of distro, so you may as well go to the source.
Do mind though it doesn’t mean it’s easy, like at all, and I fundamentally agree, there’s a million better choices for first timers.
Returning Arch user (absent since 2008/9) here, using Plasma Wayland. Overall a positive experience but there’s lots of little finicky things to setup, and I haven’t tried using linux-zen like in my EndeavorOS work laptop, I imagine that’s a bit more finicky with DKMS.
Nothing out of the ordinary for Arch thus far though, just manual configuration.
He’s decent enough to follow, but honestly his content is kinda mediocre. It’s mostly reading off news of off aggregators, distro reviews (I don’t really distrohop…), opinion pieces, and very surface level UI UX stuff (which is what he’s passionate about, after all), mixed with the usual tuber tropes like padded top X lists, clickbaity titles and the like.
I don’t even mind the clickbait, as a positive example I find NetworkChuckCoffee’s videos interesting for example, despite having all the tropes. Much more of a “get shit done, learn things” type of approach, enough to dip your toes in any given concept, so then you can go off and understand it, learn it and add it to your toolbelt. Useful.
This is one of the few things I really like about JS/TS. for (thing of things) is very legible and self documenting.
just make sure to never put it in ur anium.
If it’s just the dirty flag (it was uncleanly unmounted) you can try
ntfsfix -d /dev/sdc1
Still probably better to boot into Windows and let it deal with it (ntfs tools are still reverse engineered stuff after all), and check journalctl before doing it, but it works in a pinch.