by profwalkstr on 5/31/23, 12:59 AM with 2 comments
by gexla on 5/31/23, 3:04 AM
1. I live in an area where I have limited options for fast internet. I'm regularly running into problems with my attempts to install anything with Snap. Often the connection just times out and I can't install the Snap.
2. Snaps can be huge. This is an extension of #1. Downloads on a crap connection may take way longer, because you're downloading all the dependencies required to run the software. This is also an issue if you're poor and have limited drive space.
3. Some of the technical issues with Snaps can be perplexing for regular users. For example, it took me too long to figure out how to access resources outside of my home directory with a Snap. I later figured out the fix is to mount the location to my home directory. It's concerning how many threads I had to read through with questions and ANSWERS before I found a rock star who could explain what the issue was and how to fix it. My wild guess is that like .01% of Linux users know how this works.
by jordiburgos on 5/31/23, 9:45 AM
Each time I try to know the free space of with the command "df -h", I get a big list of filesystems starting with /snap/... Even that I never opted in to use it.