That's because we are...
If .y Firefox will once again be updated without asking me and then refusing to open any page without a restart I'll fucking lose it
Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
sudo
in Windows.Please report posts and comments that break these rules!
Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't remove France.
That's because we are...
If .y Firefox will once again be updated without asking me and then refusing to open any page without a restart I'll fucking lose it
Wait hold on wait, does that bullshit have something with Firefox being distributed through Snap?
If it does, I'm going to sn... also fucking lose it
Only tangentially related - but a friend brought over a new kubuntu install and Canonical had the cheek to demand money for VLC patches? They don't fing own VLC. What the actual f is going on over there, Canonical?
Mark Shuttleworth is a greedy bastard and itβs finally starting to show.
Haha, I break snap a lot less than the others, and it took a bit to figure out the differences. Appimages are annoying af. Flatpaks are my favourite when there isn't a good old .deb. I recently broke Flatpak though so it's on my naughty list. Snap still chugging along for some reason, I just wish the permissions weren't so crazy strict (Nextcloud).
Speaking of all this, I realised I've accidentally installed some things twice. Is there a good way to list all the different package managers together to see what is duplicated?
Hadn't snap fixed a lot of the complaints people initially had?
Has it? My complaints are: I have to use VPN software for work that replaces /etc/resolve.conf with a symlink to another location, one that sandboxed snaps can't access. There's no way to grant them access; the "slots" that you can connect are fixed and pre-defined. You can't even configure the file path; it's defined right in the source code. Not even as a #define, but the string literal "/etc/resolve.conf". That seems like poor practice, but I guess they're not going for portability.
Also, I have /usr and /var on different media, chosen for suitability of purpose, and sized appropriately. Then, along comes snap, violating the File Hierarchy Standard by filling up /var with application software.
Minor annoyances are the ~/snap folder, and all of the mounted loopback filesystems which make reading the mtab difficult.
Don't worry, Snap: Flatpak and Tarballs are NOT better by much. And, chances are, the system package manager may be lacking in so many validation requirements that it's not iso27002-compliant and thus could be junk.
There-there, Snap. Most people won't even know why you suck.
I'd love to use flatpak more, but with my peculiar internet situation, installing a single package can take 6-7 hours.
Appimage>your inferior packaged application method
Fuck flatpak, all my homies hate flatpak