• 1 Post
  • 43 Comments
Joined 2 years ago
cake
Cake day: June 19th, 2023

help-circle





  • 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?





  • 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.






  • 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.




  • 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.