• 0 Posts
  • 49 Comments
Joined 1 year ago
cake
Cake day: June 19th, 2023

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




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






  • Windows has one major thing going for it: it’s best-in-class for gaming. It might even be the greatest gaming platform of all time. Linux and even Mac are gaining ground, but they’ve got a little ways to go.

    …is Mac gaming actually gaining ground? From listening to a friend of mine who has a Mac, it sounds like Mac gaming is going steadily backwards. Wine and similar doesn’t work very well for them, and Mac compatibility is happening with fewer and fewer games. Game Porting Toolkit isn’t really for end users, is it? Is there something else my friend is missing?


  • The issue is one of licensing, not technology. There’s all kinds of patents in the space, and using free codecs could still infringe them. DirectX doesn’t have the same patent protection. I believe in theory you could make a fully open source Linux native version of DirectX.

    For more info from someone who knows more than me, see here.



  • If GE received a Cease and Desist, that would be frustrating, but linux gaming would go on. If Proton got a Cease and Desist, that could be catastrophic to linux gaming. Valve could even theoretically get banned from working on linux gaming (like the Yuzu devs got banned from working on emulation). It’s just not worth the risk for compatibility/performance for a smaller proportion of games.


  • That’s fair. It’s an all-around sucky situation regardless, and it makes sense why AMD isn’t marketing socket longevity quite as much in AM5 as they were with AM4.

    I do think losing capabilities for older CPUs in favor of new ones is pretty common for long lived sockets, and is an acceptable tradeoff for longevity imo. The board I was originally using for a 2600X never promised 5000 series support, but almost added it anyways. Unfortunately it never got beyond a beta bios, and I decided that wasn’t good enough for me (and I ended up giving the old mobo to my sister in a build for them, so it all worked out anyways).







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