If you generated the whole thing with AI, what made you think the maintainers couldn't have done this themselves?

View this comment - View article - View full comments

Guys, stick to meaningful and info rich messages on the GOL forum from now on; don't waste precious server storage space on worthless messages.

View this comment - View article - View full comments

Quoting: hardpenguinThis is getting ridiculous

GETTING ridiculous?

View this comment - View article - View full comments

Everyone is suffering just so dozens of companies continue to re-do the very same mass scale copyright infringement, AKA AI.

View this comment - View article - View full comments

Looks charming

View this comment - View article - View full comments

Quoting: Boldos

Quoting: sarmad

Quoting: rustynail

Quoting: sarmadThe snap file format and client side tools are completely open source. What's proprietary is the backend, i.e snapcraft.io, which is fine.

Doesn't that kinda mean that snap being open source is pointless to a large extent? It's like an open source client for a proprietary messaging service

Almost. Technically you can fork the snap front end to make it point to other backends, and I think someone has already done that, but practically such a fork won't be popular since the upstream is locked to a single backend and Canonical won't accept such a change to be upstreamed. I think if we didn't already have Flatpaks and AppImages such a fork would've been popular, but at this point Snap is a dying format outside of IoT.

Dying? Oh....
So why is it being installed by users on literally dozens of distros...? 🤔

Because it's not dead yet, but it will be. The deciding factor here is not the users; it's the developers; and most developers are going flatpak. Eventually, users will also switch to flatpak when they see more and more packages maintained in Flathub by the original developers, while the snap version is maintained by the community and is lagging behind in terms of updates.

View this comment - View article - View full comments

Quoting: Caldathras

Quoting: sarmadThe solution to the ethical dilemma should come from politicians, but they are unfortunately too corrupt to do the right thing.

Why should ethics be the responsibility of government? That just brings more "nanny state" interference in everyone's lives. Ethics should be personal and exercised on the individual level. The corporations will switch gears soon enough once they realize their policy is garnering very few customers.

From the perspective of legality, however, there is the matter of the violated copyrights ...

Not the responsibility of the government, rather the responsibility of the judicial system. But you'll need the politicians to amend the copyright laws to make it more clear to the idiot judges who still can't see the mass scale copyright infringement that is going on here.

View this comment - View article - View full comments

Quoting: rustynail

Quoting: sarmadThe snap file format and client side tools are completely open source. What's proprietary is the backend, i.e snapcraft.io, which is fine.

Doesn't that kinda mean that snap being open source is pointless to a large extent? It's like an open source client for a proprietary messaging service

Almost. Technically you can fork the snap front end to make it point to other backends, and I think someone has already done that, but practically such a fork won't be popular since the upstream is locked to a single backend and Canonical won't accept such a change to be upstreamed. I think if we didn't already have Flatpaks and AppImages such a fork would've been popular, but at this point Snap is a dying format outside of IoT.

View this comment - View article - View full comments

While I agree there is a lot of immorality in AI, avoiding it just puts you at a disadvantage since everyone is using it. So, you'll be harming yourself, not the unethical AI companies. The solution to the ethical dilemma should come from politicians, but they are unfortunately too corrupt to do the right thing.

View this comment - View article - View full comments

Quoting: GuestSnaps = non-free (proprietary) file format belonging to Canonical

=> No thanks, I don't want it on my operating systems

This is not correct. The snap file format and client side tools are completely open source. What's proprietary is the backend, i.e snapcraft.io, which is fine. The problem with snaps, other than re-inventing the wheel, is that it does not allow the end user to add new repos (other than snapcraft.io) like you can do with deb or flatpak.

Quoting: GuestI don't like using AppImage either, it's too cumbersome to use for launching applications and there's no built-in application update system.

This is not true either. AppImage is a modular tool, which actually is more Linuxy than the monoliths that are snaps and flatpaks. In other words, the features you get from flatpak can also be achieved with AppImage, only that you have to install multple packages. There is an appimage launcher that makes installing and removing appimages as easy as flatpak, and there is a separate tool that provides auto updates, and there is also a hub for appimages similar to flathub. There are also separate tools for providing sandboxing. Out of the three formats, AppImage provides the most flexibility: you can download an appimage directly, or use a hub. You can use it sandboxed, or not. You can have appimages auto update themselves. You can use it for cli or gui, etc. If distros adopted AppImages and have it all configured out of the box it would've been as easy to use as flatpaks, but with extra flexibility, which actually is the essence of Linux.

View this comment - View article - View full comments