I feel like there’s also the point that on Mac OS a lot of stuff “just works” because everything else just doesn’t work at all. I have a number of things that just aren’t going to work at all on Mac. Linux is obviously much more permissive, which leads to a lot more kinda working stuff that just wouldn’t work at all on Mac.
The compositors are the ones doing a lot of the protocol development. They want to have WIP versions so they can see what issues crop up, they’ve been making versions all doing. Now, I agree that it is slowing things down, but it’s more of just an additional thing that needs to get done, not so much a chicken and egg problem.
Wine and Proton have actually put a ton of work into Wayland support, it’s very far along. I wouldn’t be surprised for Proton to have a native Wayland version soon.
Also XWayland has many limitations as X11 does.
If an app has only ever supported X11, then it probably doesn’t care about those limitations (the apps that do care probably already have a Wayland version). And if an app doesn’t care about the extra stuff Wayland has to offer, then there’s not really a reason to add the extra support burden of Wayland. As long as they work fine in XWayland, I think a lot of apps won’t switch over until X11 support starts dropping from their toolkit, and they’ll just go straight to Wayland-only.
Programming languages is way too broad a category. There’s a lot of variation in both power and difficulty.
The last commit was two days ago and the last update was two months ago (at least for me on Android).
No shame in having to switch back after giving it a try and running into a lot of issues. Having to reboot a lot is definitely unusual, there’s probably something wrong with your setup, but who knows where the issue is or how long it would take you to fix. Hopefully you can give it another try in a few years and those issues have been resolved.
While this is still a massive problem, it does require a public fork at some point. So if you have a private repo that has never had a public fork, you should be safe.
From my own looking into this it looks like more of a suggestion than a request (for now at least), just a “this might be a good idea, we should look into it”.
The deleting most emails is very interesting. In my personal email, I’ve been saved quite a few times by finding emails multiple years old. But I can definitely see how things would be quite different in a work email, and I may consider trying that myself.
will not solve issues with compositors not having it
Many compositors already have patches for explicit sync which should get merged fairly quickly.
graphical libraries not having it
Both Vulkan and OpenGL have support for explicit sync
apps not supporting it
Apps don’t need to support it, they just need to use Vulkan and OpenGL, and they will handle it.
Wayland doesn’t implement sync of any kind, they probably meant to say “the Wayland stack”
Wayland has a protocol specifically for explicit sync, it’s as much a part of Wayland as pretty much anything else that’s part of Wayland.
Nvidia is not the only driver that needs to implement explicit sync.
Mesa has already merged explicit sync support.
Currently yes, tho Wine has gotten pretty far with Wayland support, so it wouldn’t be too surprising to see Wine Wayland be useable for gaming in the next year or two.
The games on Steam Deck are already running in Wayland using gamescope IIRC
I believe they’re saying that when come back from suspension, the wifi doesn’t work until they reboot.
Sounds like a “temporary” error message.
That girl seems to have dodged a bullet.
It’s a very strange place to go on fire! A fire? At a Sea Parks? It’s been racking my head!
To be fair, I imagine those rules were developed for use with physical writing, when minimizing space used up was more important. Nowadays, even as a native speaker these headlines just take extra effort to parse without much of a point.
Very high priority isn’t a number that you especially want low (or high), in fact it’s probably not good for it to be 0. It’s just what is considered important to work on. Once those are fixed, even if no new problem crops up, they’ll just relabel existing bugs that they want to focus on getting fixed.
This is in contrast to the 15-minute bugs, that you do want to go to zero.
I’m pretty sure Linux still uses Unix-style permissions in NTFS, which causes issues when Windows tries to use its own permission system on the same partition.