this post was submitted on 20 Sep 2024
384 points (100.0% liked)
linuxmemes
21180 readers
886 users here now
Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
- Instance-wide TOS: https://legal.lemmy.world/tos/
- Lemmy code of conduct: https://join-lemmy.org/docs/code_of_conduct.html
2. Be civil
- Understand the difference between a joke and an insult.
- Do not harrass or attack members of the community for any reason.
- Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
- Bigotry will not be tolerated.
- These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
3. Post Linux-related content
- Including Unix and BSD.
- Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of
sudo
in Windows.
- No porn. Even if you watch it on a Linux machine.
4. No recent reposts
- Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.
Please report posts and comments that break these rules!
founded 1 year ago
MODERATORS
Yeah. I don't mind
snap
at all for cases where a better package doesn't exist.What made me give up Ubuntu was how it railroaded me into
snap
versions of packages that work better, for me, as native.deb
installs.Oh definitely. Canonical forcing us to use snap Firefox was very shitty. I mean I still use Ubuntu because I'm lazy, but I did change the snap Firefox thing to the apt libraries or whatever.
I really don't understand why they don't just adopt flatpak.
I don't believe Flatpak has the ability to package something like node. It certainly can't package kernels or system services (at least not without leaving the user with a ton of manual work to do that would make it not much better than getting a tarball).