This game is so much fun. To me, it's the best indie game of the year, and the fact that it's done with Godot does influence my rating 😉

View this comment - View article - View full comments

SteamOS 3 is still not open-sourced, isn't it?

View this comment - View article - View full comments

I was given this video, from Gamefromscratch, that explains the merge a bit: https://www.youtube.com/watch?v=IZ9iQ9jaf2g

View this comment - View article - View full comments

Quoting: EikeWhich would be strange, they seem to be sort of a business partner with Valve here...?

Indeed... I hope the current score has been given before Valve started shipping parts of the Steam Deck.

View this comment - View article - View full comments

I find the score pretty harsh actually compared to other devices...

• iPhone 13 Pro: 6/10
• Xbox Series X: 7/10
• PS5: 7/10
• PS4: 8/10
• Switch: 8/10

So the Steam Deck is as repairable as the Xbox Series X and the PS5, less than the Switch or a PS4, but a bit more than an iPhone 13 Pro.

I think it's pretty obvious that it isn't right. How do you get parts for all these devices? I tried for a PS4 and it is not easy at all, you got to ship parts directly from China and you're not even sure it's going to be compatible! And look at how difficult it is just to get into an iPhone! And the Steam Deck gets barely better than an iPhone! On the other hand, Valve has been open from the start to the idea of opening and repairing the Steam Deck, they sent the blueprints so anybody can print whatever they want, and they even offer parts now.

I must say, I'm a bit disappointed by iFixit here, it doesn't seem fair to me.

View this comment - View article - View full comments

Will iFixit increase the repairability score of the Steam Deck now that parts are easily available?

View this comment - View article - View full comments

Disclaimer: sorry didn't have the courage to read the 8 pages ^^'

So.... I don't see the link between the kernels and the anti-cheat?! I don't know much about the ins and outs of Anti-Cheat software, so I'm doing some reading right now. Of course, I am no expert because I've read a few pages about it. But I am still an experienced developer, and have a pretty good knowledge of security overall.

I am intrigued to understand why the kernel variations are an issue for an anti-cheat software. I mean... Is EAC storing all the hashes of all the Windows DLLs, their variants, and the graphics drivers, for each releases, including the DLLs/drivers that are currently in development so that developers can test them? Seems like a daunting task.

From what I've read, the solution is more to have a unique signature send frequently to the server, proving that you are not running a different code and thus not cheating. A kernel (whichever variation you have) is basically a set of functions to talk to your hardware. I would understand that an AC software would need a very specific set of features and so the solution would be to support kernels starting from a very specific version. I'm trying to understand how modifying the kernel source code becomes an issue.

Also, security by obscurity has never been a solution. Take a look at HTTPS, it allows to have a secured connection even though everything is out in the open. There are mathematicians and researchers working on these problems (and finding solutions) since the beginning of the computer science.

So I'm confused mainly, and the answers Tim Sweeney is giving us doesn't convince me (I'm not sure Twitter is the appropriate medium for this kind of explanation, but it is what it is...)

View this comment - View article - View full comments

Flatpak packages are not very difficult to create. The sandboxing is there mainly if you want it, otherwise you can always bypass it relatively easily (it's not advised, but it's still part of the standard).

The Flatpak manifest simplifies A LOT the dependency management, you just point to the git repo and tag, or the release tarball, or a local file, or ... and it will compile almost everything for you, you don't have to compile everything yourself and package it in an AppImmage.

So yes, Flatpak can be a bit more complex than AppImage (which is basically a bundle of files), but it's just a matter of reading a few pages of documentation and asking questions on le communication channels. After that, the aforementioned complexity becomes a helping tool for the devs. And if the dev wants to dig deeper, they can see how to sandbox the shit out of their application. (I do maintain an application installable through Flatpak).

View this comment - View article - View full comments

I'll proudly rock this game on my future Steam Deck!

View this comment - View article - View full comments

Quoting: slaapliedjeThe day YouTube stops working with ublock is the day I stop using YouTube. Can't stand ads...

Well, ads are the reason why Youtube is free. Have you considered Youtube Premium or subscribing to your content creators? These are the official ways to remove ads.

View this comment - View article - View full comments