Damn right.

Oh, that makes more sense, but then “unsigned” void?

Okay, U8, sure, but a boolean is U0? Surely U1 if you absolutely must…

I’m with you on rejecting AI being sane, but the idea that gaming wikis should be integrated into wikipedia is kinda nuts. If I search “Iron” on wikipedia I’m looking for facts, not a thousand item long disambiguation cluttered with every game that has iron as a resource. Conversely, on a game wiki my search for “Iron” has an entirely different context and I’m looking for different info.

Not to mention game wikis have way lower editorial standards, their own tone (e.g. making jokes), versioning concerns, their own new user friendly homepages etc.

Wikipedia could tuck this all into a separate namespace, sure, but that’s effectively a separate wiki anyway and then it raises questions like “why is wikipedia hosting a mechanical guide for this porn game?” or “How long do we need to host the content for this game that peaked in 2012 and is now abandonware?” that are conveniently sidestepped by those communities supporting themselves.

An anti-DEI fork by a wingnut and a project that isn’t even half way ready to use starting from scratch in a niche language. Neither of which are capable of dealing with the fundamental problem of X, the protocol itself, without becoming something entirely different.

… I’m not holding my breath.

Agreed. I was an early Wayland convert because once upon a time I started writing a WM and taking an interest in X internals… And then my face melted off like I’d opened the Ark of the Covenant.

Things are so much simpler now.

I use KDE Connect remote input on Wayland all the time…

KMag is broken (simply has not been updated, not like it couldn’t work) but you can zoom the entire screen in KDE with super +/- is that not good enough?

Didn’t they straighten out Wayland support? I thought this was a thing of the past as of 555, but I also haven’t run Nvidia myself in years and years.

Wayland is a sports car - modern, tailor made for performance. X is like a '99 Civic that’s had the seatbelts stripped out and the airbags replaced with cameras that let all the other cars on the road see you naked.

It’s fine to prefer X, but the older it gets the more people are going to roll their eyes at you. XWayland is fine for random old stuff, but there is zero reason X should be running your whole display these days.

Inb4 someone mentions network transparency that gimps the rest of the system or some 5000 year old app that needs to sniff events sent to every other program.

Look on my works Sim Mayor and

I wouldn’t do a mailing list these days, but as someone who spent the early part of my career interacting with devs that preferred this method, it’s actually pretty ergonomic by a 2005 standard. A message thread aware, text based email client that can turn messages into patches in a keystroke makes it actually pretty comparable to modern code review…

I think it’s hard for younger devs to get this because they’re used to email being stuck in a crappy, unthreaded browser interface or Outlook etc. (which are terrible for mailing lists) and most collaboration taking place in code review and chat platforms like Teams/Slack but for decades before these were feasible, email was the way…