Btw just before I leave, I’ll drop this here since it seems to trigger people like you for some reason:

https://en.wikipedia.org/wiki/Bosnian_genocide

Removed by mod

What instance do you suggest?

Yes it goes back to Holodomor and how russia has always treated ukranians as second class citizens.

What rational discussion is to be had when one country is clearly annexing another since 2014 lmao?

Holy shit I didn’t know admins in this place were full blown Russian lickers. I don’t know about you but I would gladly have my country join nato if that means not ending up like Georgia or now Ukraine twice.

Also congrats on getting Finland to finally join nato btw.

You can use appimages, more importantly if you make a directory next to the appimage with the name of the appimage + .home the appimage will also set that as its $HOME that way you can also keep the configuration files of the app separated from the host OS.

You can also sandbox appimages with aisap.

It pulls the latest chromium from googleapis.com so it can do everything.

This is already done automatically.

AM puts the .desktop files in /usr/local/share/applications

AppMan puts them in ${XDG_DATA_HOME:-~/.local/share}applications

They also get symlinked in PATH, that is you can launch yt-dlp by typing yt-dlp on the terminal as if you had installed it with your distro package manager.

I wonder, is there a tool that lets me script installs?

I’ll want to check if application exists, and if so, update, otherwise, install. That kind of thing.

https://github.com/ivan-hc/AM

Use AppMan to install them in HOME.

Check this out: https://github.com/ivan-hc/AM

Use appman and set the install directory to ~/Apps and now you will be able to install appimages/binaries in the ~/Apps dir using a package manager that keeps them up to date and that you can move to any other distro, I have all of this:

Although more recently for binaries I’ve been using this instead, which pulls from a massive repo of static binaries, though note that dbin needs its own separate directory in HOME to install binaries (you can’t use ~/Apps that is).

I’m curious, what makes AppImage a good choice for the lazy developer? Is it easier to create?

The appimage is basically just git clone -> make -> make install DESTDIR=/path/to/AppDir -> wget appimagecreationtool and finally appimagecreationtool /path/to/AppDir and that’s it you have your appimage.

appimagecreationtool being several tools that can create the appimage from an AppDir, like linuxdeploy, linuxdeploqt, go-appimage, etc

And that on itself isn’t complex either, it if basically running ldd on the binary, then copy those libraries into the AppDir and finally run patchelf to patch the paths in the binaries and libraries, suyu uses a deploy script instead of using those tools, which I’ve recently forked and began expanding.

I don’t know how easy it is to make a flatpak or snap, but I do know the dev of zen browser hates dealing with the flatpak and iirc right now the flatpak is outdated as result.

EDIT: Also lite-xl has been making a flatpak for like 2 years and it isn’t ready yet.

Glad you like AM.

. If you end up with 4.7GB for runtimes, that’s basically nothing these days

Yes but that wasn’t the original comment I replied to was about.

163 flatpaks and the runtimes used 8.7GB

163 flatpaks using 8.7 GiB means that the average flatpak is using 54.6 MiB.

That’s good the other time I got this linked: https://tesk.page/2023/06/04/response-to-developers-are-lazy-thus-flatpak/#but-flatpaks-are-easier-for-end-users

Which is no good as in that example there was 173 flatpaks using 27.66 GiB, average 160 MiB, while in your case the average flatpak is using 91 MiB.

This is what I have with appimages:

In this case the average appimage is using 69 MiB, though there is one outliner which is the Steam appimage that I have there (470 MiB) which is an entire conty container with its own video drivers and everything, without it the average would be 56 MiB.

I know this doesn’t matter these days but once again that wasn’t what the original comment was about.

Well we are talking about two gigs, after all. Unless you’re using an embedded system, it’s not a much of a concern if you ask me. But it is more, true

Thanks for the link showing an average flatpak using 54 MiB though, didn’t think it was possible lol.

WAIT I just took a deeper look at the link, isn’t that guy just showing the runtimes without the applications using 8.7 GiB?

I tested installing some web browers, kdenlive, yuzu and libreoffice and without knowing I ended up with 3 different runtimes and the total storage usage (with deduplication) was 4.79 GIB.

Meanwhile with 33 appimages that I have (which includes same flatpak apps I mentioned) are using 2.2 GiB.

It doesn’t matter if they share if in the end they end up using several times more storage than the appimage equivalent.

Isn’t the gnome runtime alone 2GiB? You know how many appimages that is?

Not to mention you are unlikely to only use one runtime.

I’m pretty sure sbin originally meant static binaries and not system binaries lol

posix sh + awk for manipulating data?

It makes me mad to see the current state sway is in, I even bought an AMD GPU for nothing.

I really don’t know lol

Increasing the max_map_count is needed for some Steam games, iirc Arch is now dong this by default.

iirc the dirty_bytes settings prevent the system from hanging if there is too much disk IO

And setting transparent_hugepages to madvise was something I did when archlinux had this bug in the kernel: https://old.reddit.com/r/archlinux/comments/1atueo0/higher_ram_usage_since_kernel_67_and_the_solution/

It was eventually fixed but I later ran into the issue again and I decided to keep it on madvise.