It’s EAC, which is kernel level on Windows but not on Linux. I guess they wanted to go full kernel-level anti-cheat.
It’s EAC, which is kernel level on Windows but not on Linux. I guess they wanted to go full kernel-level anti-cheat.
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.
Ah, gotcha. Sorry about the confusion.
OpenRCT2 ditched assembly tho. They wrote it entirely in C++.
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.
Steam is a massive worldwide market, and the Steam Deck isn’t offered everywhere. Chinese users for example have to import it, so not many are used there.