And still not at X11’s level. I daily Wayland, but this is extremely disappointing as a photo editor.

Thank you :). I understand your perspective better. I still think we oughta avoid the buzzword factory but this isn’t that kind of issue.

As a devops professional I understand your points perfectly here but IMHO container native is a much better more descriptive definition. Normies see cloud and think hyperscalers and big tech, not the CNCF. They don’t understand it and it’s our/your(/the CNCF’S) duty to make the concepts more accessible IMHO.

Are they based on Firefox ESR? That made me quit Floorp, it was pretty disappointing to be on a legacy reskin of Firefox.

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.

I had a quick go at it yesterday (the latest 535 broke DDC CI for one of my monitors, making plasma-powerdevil unable to start) and for whatever reason KWin ran at something like 3 seconds per frame. No that’s not a typo, I mean it. I hope it’s fixed before it gets to Arch’s repo.

EDIT: It works! I had to switch to the DKMS driver (the main one isn’t in the repos yet) but other than that my Wayland session didn’t die a horrible death. Well smooth. I still didn’t test much, but at least night light works.

Yeah, as usual the opinionated crew are making something that one may even like feel like it’s forced down everyone’s throat (see: systemd, snap…) and making everything worse. I don’t see how any Linux desktop distro worth its salt can get by ignoring 90% of the PC GPU market share and essentially forcing them into an inferior desktop experience for pure ideology’s sake, and I LIKE Wayland. I even put up with all its quirks in a particularly quirky implementation (KWin). But this ain’t it if you want users to use your OS.

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.