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.

I have a giant FLAC collection and I sometimes wish I could use these local players because I used Winamp/XMMS/quod libet back in the day, but I feel like I just can’t give up consistent access from outside the house.

I ran Tauon for a while (and have run a few of the others over the years) but I always end up back at my Airsonic setup. Works in any browser, works in a few different Android apps (Subsonic compatible), less of a pain than mpd.

Maybe it’d be different if I was still sitting in front of my computer virtually all the time, but nowadays phone to Bluetooth speaker/car/Chromecast is like 90% of my listening.

Basically, the executing thread might get interrupted in a window of code where the interrupt flags are wrong. Not looking at the specifics, but this could lead to various things from mostly harmless (e.g. potentially holding a lock for many times longer than expected but eventually releasing it) to program crashing (e.g. if taking an interrupt while handling the fault leaves the data structures in an inconsistent state).

This is likely the first one, since it was missed for so long in a very well exercised piece of code.

Are you running the native version or through Proton? When I played Civ VI the Linux native version performed worse than using Proton, ironically. Either way, maybe try switching?

Since you specified multiplayer I’m guessing it’s not time to load from disk or anything.

For ancient stuff, maybe, but AMD is also active in enabling new stuff in the kernel and userspace. AMD basically invented Vulkan, and have had the best open source driver stack for years at this point.

I love what Valve has done for Linux, but it’s the last mile of track at the end of huge amounts of outside work enabling the hardware to work in the first place.

I have a wife stuck in the Adobe-verse and yeah, going back that far should work great. It didn’t become a huge hassle until they started being insane with the licensing.

I burned a Blu-ray a few years back just to supplement some of our encrypted Google Drive backups with copies that would be more accessible in case of my demise, or physically grabbable in case of disaster. I know they won’t last forever, but if Drive shut down on the same day my local copies failed at least I have an option.

Otherwise, I haven’t used physical media in years. I got the 4K LOTR set when it came out and tried to use it, but it ended up being easier to just pirate the rips like anything else.

Linus’ apathy may keep ten different competing security ideas from each being mainlined, but it’s not impossible for them to continue and prove their worth out of tree until some sort of coherent best practices are established.

Meanwhile, actual security issues will continue to be patched as needed and Linux remains the most analyzed and targeted kernel in the world.

So traditional it’s like a Norman Rockwell painting.

I agree, but I can envision scenarios where you are integrating into someone else’s workflow/machine and they (or their build system etc.) are expecting a shell script. Python is ubiquitous but sometimes you just want to work like everything else.

Definitely agree. Had a couple of them and loved some of the ideas (touchpad sticks, gyro to mouse aim, all of the Steam Input flexibility) but they never really eclipsed my rechargeable Dualshocks in terms of feeling right. Taking some of the Deck’s refinements and giving it another spin is welcome.

I put this on expecting a trainwreck and a cash grab too, but it still had me laughing my ass off. It really felt like they understood why the originals were so funny.

Yeah, my parents are still basically the same liberal Democrats they were when I was a kid. Meanwhile I’ve gone farther left and the rest of the family mutated into a virulent strain of fascist.

In a weird way this makes Linux a microkernel. They’re “macro” but isolated and cooperative. Coolest patch set I’ve read about in a while.

You are getting this from Xwayland, so you’re running a rootless X server in the background. It’s nice that it works seamlessly, but it’s not really Wayland doing anything but managing the X window.

This is about Linux kernel driver maintainership… It’s all open source.