The Battle(non)sense from the blog post is super interesting! Apparently, limiting your framerate has a better impact on the input lag than these algorithms:
https://www.youtube.com/watch?v=7CKnJ5ujL_Q [External Link]

View this comment - View article - View full comments

Quoting: STiATI actually have my issues with dockerized applications and kubernetes, I do not see a real benefit there but to be able to scale up and down for single applications fast.

I think the best way to summarize the benefits is the "pets vs cattle" paradigm: https://www.hava.io/blog/cattle-vs-pets-devops-explained [External Link]

View this comment - View article - View full comments

Ok, to really put the emphasis on the dishonesty of the case against Flatpak (which apparently tends to trigger me more than it should :grin:):



So lets see what a user can see when he wants to install Steam for instance:



"Potentially unsafe".. doesn't seem like it claims to be sandboxed and the safest. It simply says that it's not perfect.

But Steam is a proprietary app.. maybe on an open source app, they are less strict? Let's see GIMP:



Well, look at that! "Unsafe", it's even stricter even if it's an open source app.

I really do wonder how a regular user would think Flatpak is safer than any other solution. For them, it's only a simpler way to install open source and proprietary applications.

Oh and one last thing: I agree that it is not the most secure package manager in the world, but it is more secured than the distribution-specific package managers (e.g. dnf, apt, pacman, ...).

An application installed through these managers have literally access to anything all the time. It's like a flatpak application but with all the permissions possible. At least with Flatpak, you can limit these accesses.

The most modern applications uses the portal APIs, so they only get access to the files (or other resources) that the user accepted, and we're not talking about access to /home, we're talking about access to one specific file only, because thanks to portals, it's dynamic. You can even select a file and force it to be read-only for the applications your using. But there are portals for networks, webcams, screencasting, bluetooth, etc.

And when applications didn't implement portals, they can set default permissions in the application manifest. Like, for instance, access to network and access to the user's directory. But the user's directory is still better than having access to the entire filesystem (which is what happens for applications installed through the distribution package managers)! Not using the portals is still what compose most of the Flatpak applications, but it's because portals are fairly new, and it takes time for applications to upgrade to new standards, but it's getting there.

And finally, we might find to ultimate bad Flatpak applications that give access to the whole system. Well, guess what? it's just like an application installed through the distribution package managers.

Edit: I've continued to read and found this gem in the "Local root exploit? Minor issue!" section:

Flatpak developers consider this a minor security issue [External Link].

If you look at the link, it is a link to a minor release, as defined by semantic versioning [External Link]. If it does not add, change or break a feature, it's a minor release. My god, this person has absolutely no idea how software development works and he's made this page? (I am a software developer btw)

View this comment - View article - View full comments

Quoting: sudoer

Quoting: CyborgZetaGood. I want to see more Flatpak adoption.

Me not at all. https://ludocode.com/blog/flatpak-is-not-the-future [External Link]

This is on side of the story, I suggest you read this response to the blog post you sent: https://blogs.gnome.org/wjjt/2021/11/24/on-flatpak-disk-usage-and-deduplication/ [External Link]

Edit: there is also https://flatkill.org/ [External Link] (on the against side). These are highly opinionated blog posts, they tend to show only the numbers they want to show and hide the other because it goes against their beliefs. I tend to take these kind of blog posts with a HUGE grain of salt.

View this comment - View article - View full comments

I really love Flatpak. There are some issues, it's true, but they are arguably being ironed out as we speak. In the end, installing applications and getting the latest upgrades have never been so easy.

On top of that, as developers and their tools get more knowledge of Flatpak features, security will become better and better (e.g. with sandboxing*).

* I know the current state is not perfect, but if Flatpak was too strict on security right from the beginning, it wouldn't have been popular and we wouldn't be having this discussion about OBS officially supporting Flatpak. The community would probably have turned to Snap or, worse, AppImage.

View this comment - View article - View full comments

How do you use retroarch on Steam??

Edit: oh! It's actually an application to install within Steam itself! https://steamcommunity.com/app/1118310 [External Link]

View this comment - View article - View full comments

Apparently communication between System76 and GNOME is not exactly as System76 describes it: https://blogs.gnome.org/christopherdavis/2021/11/10/system76-how-not-to-collaborate/ [External Link]

View this comment - View article - View full comments

There's also 20% off of Hokko Life (ProtonDB: platinum [External Link] and Hell Let Loose (ProtonDB: borked [External Link]. @Liam, do you know if these games have native Linux builds?

View this comment - View article - View full comments

I think I need to play this game as I know it will touch me deeply and may even help me with my mourning.

Thank you to the devs for having done this game and level up the media as a whole!

View this comment - View article - View full comments

It's nice from Kythera to offer a community license, but I think it defies the purpose of a fully open-sourced 3D editor.

As a dev, if I were to choose O3DE, it's because it's open-source and therefore there are no ties to any other company and I can easily maintain my project for the years to come, I simply have to snapshot my game code and data. But if I start to use proprietary modules, then I'll be limiting myself to the module company's terms of service, thus defying the long-term maintenance.

I think, if it's not already the case, that an AI module should be open-sourced and included in O3DE ASAP.

View this comment - View article - View full comments