Spoken like someone who’s never used nix before lol.

Good luck even having a question to ask, much less finding where to ask it

We laugh to hide the tears

(Error: infinite recursion detected)

I mean it won’t work if you rip out your hard drive either, but usually things are custom managed in those situations by whoever created them.

(Ex. Nixos is the same, but not really a problem cause you expect to manage it within nix)

SIMD Might be the term youre looking for (Single Input Multiple Data)

Can’t fake googles key signature

Why not? :(

Done it plenty of times before using nixos on SBC’s, its a ram hog when rebuilding

Swap space could help install a slow Linux DE, if youre still inclined

So?

Using the right build platform you could design a single flag to enable automatic appimage building as well.

Just seems like a cleaner build environment to me, exactly what you’d want to gaurentee things remain distro agnostic

Some desktops connect to servers on occasion, it was pretty big back in the 80s

You can read more about it here

JK Rowling🤢

Its like locks on a car, sure someone can still break the windows - and if still worried you should just use an armoured car.

But for most of us locks are more than enough to keep people out our shit

Doesnt even give access to the camera subsystem’s embedded flash memory, essentially useless

/s?

The mentioned guix or more popular nixos arguably handle this better than traditional distros

Nixos because… I feel like were already loud enough of a crowd everyone should know its benefits lol

If you’d prefer native to using an unpopular tool thats archived since 2023, try this site.

All you have to do is click on the revision you want to install, and it provides instructions to install it (having the benefit of being actually using the native package manager instead of just storing some binaries somewhere exclusive to the app)

Surprised there was a non-nix way to achieve this honestly, even if it is a bit hackey

Man doesnt even know distrobox exists

(Or flatpak of appimages or any other containers)

Good luck even finding something not in nixpkgs though

GCVE is more confusing if anything

Sounds like flatpaks/appimages with extra steps

Includes all dependencies? ✔️

A single file? ✔️

Independent of host libraries? ✔️

Limited learning curve? ✔️

Not sure how appimages handle it internally, but with flatpaks you can even be storage efficient with layers, whereas 100s of static binaries could contain an awful lot of duplicates.

Can’t see why you dislike appimages, sure not 100% size efficient - but for one off binaries youre probably not spending much time optimizing anyways.

Not that you couldnt make an appimage 2.0 solving all your issues, but we’d just be back to that package manager xkcd all over again

From a comment on the article

I love compression, I love ffmpeg and I love more performance, but… FFV1 is ffmpegs own, old lossless compression format for archival purposes. It is not particularly bad, but it is also not particularly good or modern.