What’s wild is that one of the people who write anti-cheat software was saying they needed to get their shit working on Linux like yesterday.

So I mean, it crazy that Windows is literally having some folks scramble on how to get their shit working on Steam/Linux.

Yeah, I think that’s the bigger issue here. These devices pay their way by collecting data to sell off. What this “overhual” is indicating is that they haven’t quite figured out how to make these devices not only pay for themselves, but also, generate a net background profit for the company.

The only thing I’m reading from this story is that Amazon is just aiming for more dollar signs from Alexia. I’m going tell you in the day and age of Siri and Whatever Google’s thing is, this is going to backfire massively on Amazon. This will likely collapse whatever paltry Alexia that’s out there. And I have a good feeling they’ll look at this collapse as “well the technology just isn’t a good money maker.” No you idiots, it’s not a mass profit driver. I get how something not drawing double digit percentage gains is a mystery to you all, but just because you cannot buy your fifteenth yacht from it, doesn’t mean that the technology is a failure.

But it’s whatever, Amazon’s ship to wreck.

I am so sorry this got so long. I’m absolutely horrible at brevity.

Applications use things called libraries to provide particular functions rather than implement those functions themselves. So like “handle HTTP request” as an example, you can just use a HTTP library to handle it for you so you can focus on developing your application.

As time progresses, libraries change and release new versions. Most of the time one version is compatible with the other. Sometimes, especially when there is a major version change, the two version are incompatible. If an application relied on that library and a major incompatible change was made, the application also needs to be changed for the new version of the library.

A Linux distro usually selects the version of each library that they are going to ship with their release and maintain it via updates. However, your distro provider and some neat program you might use are usually two different people. So the neat program you use might have change their application to be compatible with a library that might not make it into your distro until next release.

At that point you have one of two options. Wait until your distro provides the updated library or the go it alone route of you updating your own library (which libraries can depend on other libraries, which means you could be opening a whole Pandora’s box here). The go it alone route also means that you have to turn off your distro’s updates because they’ll just overwrite everything you’ve done library wise.

This is where snaps, flatpaks, and appimages come into play. In a very basic sense, they provide a means for a program to include all the libraries it’ll need to run, without those libraries conflicting with your current setup from the distro. You might hear them as “containerized programs”, however, they’re not exactly the Docker style “container”, but from an isolating perspective, that’s mostly correct. So your neat application that relies on the newest libraries, they can be put into a snap, flatpak, or appimage and you can run that program with those new libraries no need for your distro to provide them or for you to go it alone.

I won’t bore you on the technical difference between the formats, but just mostly focus on what I usually hear is the objectionable issue with snaps. Snaps is a format that is developed by Canonical. All of these formats have a means of distribution, that is how do you get the program to install and how it is updated. Because you know, getting regular updates of your program is still really important. With snaps, Canonical uses a cryptographic signature to indicate that the distribution of the program has come from their “Snaps Store”. And that’s the main issue folks have taken with snaps.

So unlike the other kinds of formats, snaps are only really useful when they are acquired from the Canonical Snaps Store. You can bypass the checking of the cryptographic signature via the command line, but Ubuntu will not automatically check for updates on software installed via that method, you must check for updates manually. In contrast, anyone can build and maintain their own flatpak “store” or central repository. Only Canonical can distribute snaps and provide all of the nice features of distribution like automatic updates.

So that’s the main gripe, there’s technical issues as well between the formats which I won’t get into. But the main high level argument is the conflicting ideas of “open and free to all” that is usually associated with the Linux group (and FOSS [Free and open-source software] in general) and the “only Canonical can distribute” that comes with snaps. So as @sederx indicated, if that’s not an argument that resonates with you, the debate is pretty moot.

There’s some user level difference like some snaps can run a bit slower than a native program, but Canonical has updated things with snaps to address some of that. Flatpak sandboxing can make it difficult to access files on your system, but flatpak permissions can be edited with things like Flatseal. Etc. It’s what I would file into the “papercut” box of problems. But for some, those papercuts matter and ultimately turn people off from the whole Linux thing. So there’s arguments that come from that as well, but that’s so universal “just different in how the papercut happens” that I just file that as a debate between container and native applications, rather a debate about formats.

KDE: Welcome to Linux. Do you like the UI of Windows? Well we have an excellent offering for you if that’s your choice. There’s also other DEs that you may select from if that’s your choice.

Windows: Here’s an ad bitch, fuck your choice.

“The mature and responsible thing to do would have been to add a content security policy to the page”, he wrote. “I am not mature so instead what I decided to do was render the early 2000s internet shock image Goatse with a nice message superimposed over it in place of the app if Sqword detects that it is in an iFrame.”

I submit the Internet axiom of: there’s times and places for a measured and reasonable response, and the other times are funny af.

Let this be a lesson to you—if you are using an iFrame to display a site that isn’t yours, even for legitimate purposes, you have no control over that content—it can change at any time. One day instead of looking into an iFrame, you might be looking at an entirely different kind of portal.

Bravo.