• 1 Post
  • 48 Comments
Joined 1 year ago
cake
Cake day: March 4th, 2025

help-circle

  • You’re the problem in this conversation because you keep tripping over the smallest things. You start talking about how there’s no update process for AppImages and then you tell me not to talk about updates but only talk about installing things when I comment on that. You’re indistinguishable from a sealion right now, so I’m out of this conversation. I never said Linux was perfect, that was a figment of your imagination. I just said that every OS has a learning curve. Stick with what you like or work to help fix what you don’t like. Yapping about it in the way you have done so far is not helping anyone.


  • The same goes for Windows. Someone who grew up on Macs will have to learn the particularities of Windows or Linux just the same if they wanted to switch to either. Every user has got to put their own effort into learning the ropes. It is no different with anything else in life. You can’t just expect everything to be handed to you on a silver platter. I grew up on MS-DOS and Commodore BASIC. Then came Windows 3.x and GEOS, Workbench on the Amiga, and eventually Windows 95. I had to learn each and every one of their particularities as I moved between them. Windows XP? Windows 7? Windows 10? Each one came with changes people complained about. Mac has had its upsets as well. Linux changed from its UNIX beginnings to have the variation we have today. Find something which looks like you want to learn the ropes and stick with it. Or don’t and go touch some grass, I guess.



  • It is more confusing on Windows though.

    I only have to look at the family members I have who have dozens of versions of .exe and .msi installers for the same program littering their Downloads folder, and then for some reason those unpack to subfolders in C:\ and leave their unpacked installer files there without any good reason for it.

    Why not just use the temp folder and remove them afterward?

    That’s on top of Windows itself littering the drive with temporary files, installer files or otherwise.

    People who have been using Windows since the early days are still trying to figure out how to clean up after it, and every iteration is made more confusing by Microsoft.

    Cleaning up installers when pulling things in through your package manager is a cakewalk in comparison.

    Considering how appimages are mostly self-contained there’s little to clean other than the single file which you run it through, and the few configurations left in ~/.config or ~/.local/share. Easy peasy.

    I have less experience with Flatpak but I’m sure it’s similarily easy to find out. I’m never touching snap again after trying it once because it’s beyond dumb.

    Of course if you build from source through git or otherwise, you’re going to have to make sure you remember where you put things.

    Everything on Windows is just so much more confusing than it has to be. And that’s without touching on the whole licensing bs or the way you may find some programs in the installed program list in the system configuration window and some aren’t in there for reasons unknown… Where’s the uninstaller in that case? Oh, the uninstaller isn’t there anymore? Try and figure out how to uninstall the program that doesn’t want to uninstall.

    Let’s take programs like Avira or Avast or whatever program which embeds itself in your registry and five or six different folders. You try to uninstall it, it claims to have uninstalled, but then Revo still finds thirty different registry entries and whatnot.

    It’s easier on Linux. By far.



  • digiKam is just in the Debian packages and easily installable via the package manager. YMMV depending on your distro. I guess that’s what your complaint amounts to.

    Linux is about having the choice to use what you want to use. If something is too difficult or annoying for you, switch to something else.

    You have that option on Linux.

    Don’t like using snaps? Don’t use Canonical’s bs. AppImages work on just about everything when they’re available.

    Deb/rpm/whatever depends on your package manager, so you should really just use what your package manager supports. Don’t use rpm on Debian, don’t use deb on Fedora.

    It’s really not that hard to grasp.





  • In case anyone needed a better explanation of what REISUB stands for:

    R.E.I.S.U.B.

    Raising Elephants Is So Utterly Boring

    R.E.I.S.U.B. is a key sequence used on Linux systems to safely reboot a frozen or unresponsive computer. It is often referred to as the “magic SysRq key” (System Request key) and allows users to perform low-level commands to safely recover or restart the system.

    The acronym R.E.I.S.U.B. stands for the specific sequence of commands you can execute to reboot the system safely, even if the system is otherwise unresponsive:

    R - Raw mode (take control of the keyboard back from the X server). E - End all running processes cleanly (sends SIGTERM to all processes). I - Immediately kill all processes (sends SIGKILL to all processes). S - Sync the disk (flushes data to disk to prevent data loss). U - Unmount all file systems (remounts all filesystems as read-only). B - Boot (reboots the system).

    How to Use R.E.I.S.U.B. Safely

    Hold Alt and SysRq, and then press each letter separately in the order of R-E-I-S-U-B. However, often the SysRq key is a dual purpose key which needs another key to activate the secondary function. For example, on a Acer keyboard SysRq is a secondary function of the Delete key and the Fn key is used to select the secondary function. So on this keyboard it would require holding down the Alt + Fn + Delete to activate the SysRq function.

    From http://pclosusers.com/wiki/index.php?title=REISUB_reboot_your_system>