If I’m reading the merge correctly, the Wayland bugs aren’t fixed, PCSX2 just added enough workarounds to consider things working.

I haven’t done it in a bit, but you should be able to do Windows startup repair from a USB (possibly a Windows install USB), which I believe can restore the bootloader. I’d recommend disconnecting all drives other than the Windows one when doing the repair.

Transporting large quantities of electricity isn’t easy, you have to have large enough interconnects to handle the energy you’re moving around.

Yeah this is a big part why I’m very skeptical of Signal. It feels a lot like Ubuntu’s snap store, it’s technically open but you can’t really interact with the main corporate controlled ecosystem.

From what I understand there was also a bug involved that caused build failures without the sdk.

Did you read the article? It’s talking primarily about how this could be really good for consumers.

deleted by creator

On a theoretical level, food calories represent a specific amount of energy that can be extracted from food. So some kind of calculation could probably be made as to how much work is required to operate the exercise bike, which probably depends on your height and weight. That work uses a certain amount of energy, which is probably equated into calories.

All that said, I have no idea how accurate that would be. And in the end IIRC there’s a bunch of other factors that affect how humans burn calories and gain or lose weight, so in the end the calorie burning stats only really need to be comparable to other calorie burning stats. So I think the bigger question is: Do different exercise equipment types put out comparable numbers?

It’s only illegal federally to gerrymander to dilute minorities. Otherwise it’s up to the individual states.

I think “speed up Wayland development” isn’t quite right, tho it will probably feel that way to end user. It’s about getting experimental protocols into the hands of users in a formalized manner while the stable protocol is still being forged. This already exists in certain forms e.g. HDR support being added before the protocol is finalized, but having a more formalized system is probably pretty helpful for interoperability, e.g. apps having to work with different DE’s.

My biggest is concern is whether there’s a possibility this will actually slow down Wayland development by pulling attention away from the stable Wayland protocols in favor of Frog Protocols. But hopefully the quicker real world usage of the new protocols will bring more benefits than the potential downside.

If you’re worried about the lack of Unix-style permissions and attributes in NTFS

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.

In the long-term yes, but in the short-term and even medium-term, housing takes time to build, so there’s going to be a lag. During that lag, it can cause problems even without NIMBY policies.

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.

For a very long time people will also still need to understand what they are asking the machine to do. If you tell it to write code for an impossible concept, it can’t make it. If you ask it to write code to do something incredibly inefficiently, it’s going to give you code that is incredibly inefficient.

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.