I used KDE for my forays into Wayland.

Bear in mind that each desktop environment has its own implementation of Wayland, meaning each can offer vastly different user experiences

Funny you mention that, as that's (at least closely related to) one of the things I was alluding to when I mentioned design deficiencies in Wayland. The way I understand it is each individual Wayland compositor is free to create their own protocol for stuff like screenshots, and then the Wayland team will take the parts of those protocols and then combine them into the Wayland protocol for e.g. screenshots, which compositors then go back and replace their protocol with that one. Which sounds great on paper, but it leads to a problem I'll call Ecosystem Lock-in, I don't quite like that term, I don't think its fully accurate, but it's all I can think of for now. What happens is in order for a screenshot program to work on a given compositor they have to interface with that compositor's screenshot protocol, and it's a lot of work to support every compositor under the sun, so most devs just won't. (Which is fine, great even, I think devs these days try to support too much stuff). But say you don't like Spectacle (Spektacle? I don't remember), your options are limited to whatever supports KDE's screenshot protocol.

Or say you're just moving from an X11 based DE and giving Wayland a try. In the process of moving over you discover your nifty little scrot based screenshot script no longer works. After some research you discover that scrot is X11 only, and the Wayland equivalent is grim, so you get your scripts converted over but they still don't work. More research later you learn that grim doesn't support KDE's screenshot protocol, and Wayland compositors basically get to do whatever they want in terms of protocol design/implementation. This is what happened to me, and caused me to give up on Wayland.

I'm still using xfce; after running into problems with Wayland the three times I tried it, I decided Wayland isn't really for me. (In fairness one of those was nvidia being nvidia, but the other two are what I consider design deficiencies in Wayland itself)

Well that explains the strange bug I started encountering in xfce recently. I guess I'll be spending tomorrow researching DEs, though I'll probably end up just using TDE or maybe CDE.

EDIT: clarified that the bug is in xfce, not xfwl.

Your use of Luddite as a pejorative outs you as willfully ignorant of both the matter at hand and the history of the Luddite movement. Your alignment with the corporate narrative here makes you sound like far more of a republican than any "AI" critic I've ever seen. Especially that "foreign operative" call out, that's peak republican right there.

Honestly, same. I initially dismissed Zig due to their insistence on making unused variables an error even in debug builds but if they keep this up I may have to just Get Over It.

It is, just not in Arch Linux itself, which is what your comment is saying.

Minor clarification: your Arch Linux link is for archinstall, the easier install script, not Arch Linux itself. IIRC it's not even the officially recommended way to install Arch.

Not necessarily, this only implies that computers are a part of a set of things that can be neither spiteful nor horny, and things that can be neither spiteful nor horny must never make art, not that all things that can be neither spiteful nor horny are computers.

I'm not too sure, I didn't look terribly deeply on that front since that's not something my group uses often, and its difficult to test on my own. That said, I believe Matrix does have some level of voice chat support, though AFAIK its more similar to Skype's calls than Discord's drop-in/drop-out voice channels. No idea about XMPP though.

I belive just Matrix and XMPP.

From my digging on alternatives the main contenders are (in no particular order)

• Stoat
  • Essentially 1:1 on discords format
  • UK based, so its future there is uncertain
  • Infrastructure is lacking, was crippled by the initial influx after discord's announcement.
  • Missing some minor UI and UX features, feels unpolished.
• Spacebar
  • Reverse engineered discord
  • Greatest potential, IMO, but as of a few days ago all it has is potential.
  • lacks significant client development, relying on an external client named Fermi, which feels quite amateurish.
• XMPP
  • Highly mature, looks very promising, but lacks any kind of guild/nested channel grouping support which makes it unsuitable for my group, so I didn't look too deep at it.
• Matrix
  • IMO the most likely discord successor.
  • Minor functional hiccups, that vary from client to client
  • Of the clients I tested, Cinny is the most discord like, but I hear commet is closer.
  • Nested spaces provides the minimum format equivalence.
• Fluxer
  • Slightly sus vibes
  • Lacks self hosting instructions
  • Media is non-permanent, which is I guess fair to keep infra costs down, but its unsuitable for my groups media usage habits.
  • Looks promising, but I've not actually tried it given the lack of self hosting instructions.

One thing that's wormed its way onto the to do list that haunts the back of my mind, is I'd like to see if I could abuse the matrix or XMPP protocols to get some of the nicer discord-like features lime invite links, server side channel ordering, and space membership over channel membership. But that's unlikely to happen any time soon.

EDIT: Forgot Fluxer. Added.

Where are you getting three years of abandonment from? The branding repo OP linked was last updated 10 months ago, while the server repo appears to have had pretty steady development for the last month at least (as far back as I bothered checking on mobile)