Did we kill Linux's killer feature?
Did we kill Linux's killer feature?
A few years ago we were able to upgrade everything (OS and Apps) using a single command. I remember this was something we boasted about when talking to Windows and Mac fans. It was such an amazing feature. Something that users of proprietary systems hadn't even heard about. We had this on desktops before things like Apple's App Store and Play Store were a thing.
We can no longer do that thanks to Flatpaks and Snaps as well as AppImages.
Recently i upgraded my Fedora system. I few days later i found out i was runnig some older apps since they were Flatpaks (i had completely forgotten how I installed bitwarden for instance.)
Do you miss the old system too?
Is it possible to bring back that experience? A unified, reliable CLI solution to make sure EVERYTHING is up to date?
You're viewing a single thread.
Depends. Unless you're on Ubuntu or Elementary, Flatpak and Snap are optional. When I'm on Arch, btw, I don't bother with any of those and just use the AUR with a helper like yay.
But I find the convenience of Flathub too good to pass up on other distros. I have been using Linux long enough to remember when the only options if your distro didn't ship something were to compile from source or to use a sketchy installer script, because Flatpak didn't exist. And as others mentioned, if you're using a full desktop environment, it likely can update everything at once via the GUI.
I don't bother with any of those and just use the AUR with a helper like yay.
Normally I do that too but recently wanted to install an app from AUR that ran out of memory during compile on 4 GB of RAM. So being able to use an appimage or flatpak was still useful.
You could have just added a swap file
And I would die of old age waiting for the compile to finish.
Swap is not "disk RAM". It's used for storing pages that go unused for extended periods of time. It's an optimization system designed to be used during normal system operations.
Technically it could solve some mild out-of-memory situations if given enough time but in practice the disk access is so slow compared to RAM that for all intents and purposes your system appears to freeze so you get bored eventually and reboot it. An attempt to compile a large application under these circumstances would last a very long time indeed.
If anything, you should disable swap in such a situation. Without swap the compile process would crash instantly when growing out of memory, with swap your system freezes.
Swap space is also used for storing a compressed dump of RAM during hybernation but that's a special case.
Yeah, I know how swap works. I'm lazy and it would accomplish the task if needed, I've done it many times before in similar situations especially on low RAM Gentoo machines.
Agreed, it's slow as fuck. It also gets the job done without going outside the package manager.
There are lots of options. You can also setup a swap file in memory that uses compression. Since swap tends to compress really well, you can allocate more memory than you have RAM and still not use slower swap on a HDD or SSD.