zbecker

@ebits21 @burgersc12

Oh shoot I didn't know about C-n. Thanks for that.

@Melco @eager_eagle

I never used portainer. Imo KISS is the best policy

@lambda

Oh, good on valve for making that easy to undo, albeit until you update.

@lambda

Oh I didn't know, I just remembered reading that it utilizes an immutable filesystem and thought that it also doesn't give root access as well. That's good to hear though.

@lambda they should if you use the single user command. The command that does it for the whole system requires root access, something you don't have on the deck.

@kmkz_ninja @OrnateLuna

I know people who use linux mint (or other distros that aim at user friendliness) who literally never have to touch the command line. This claim that you need to use the command line was true 5 years ago, but today it is largely false.

I am in a Linux User Group and I am literally the only person who uses a tiling window manager (I use hyprland) instead of DEs like kde, gnome, cinnamon, etc.

@lambda a lot of people do nix-env -ia nameOfPackage. I would recommend doing it properly with a file, and you just direct that command to the file (I would probably setup an alias). It gives you that declarative nature that nix is known for.

@lambda it's not a Lemmy server, it's a mastodon server. I assume it has something to do with that.

@lambda @BeigeAgenda

Imo a better alternative to flatpak is the nix package manager, but as I said to the other guy this'll most likely end up a VHS/betamax situation.

Both things are trying to solve dependency hell in different ways. Flatpak just builds and runs everything in a container, where as nix sets up virtual environments and builds things in isolation with per package dependency trees in an effort to make builds entirely reproducible (to the point that no matter what system you compile on, you will get the same hash).

Edit: as the other guy said, just use your systems package manager unless it doesn't exist in the repo and you can't be bothered to package it yourself. It's the standard recommended method.

@orcrist @lambda

There definitely is a problem that flatpak is trying to solve. That problem is dependency hell.

This most often (or rather most famously) occurs with python packaging. Sometimes you can have one package that requires a version that is incompatible with another version that another package requires. That's why people use python venv these days (or just use pipx).

IMO a better way of solving this is with nix. With nix, it doesn't require a container, it just builds in isolation.

Thing is, this will probably end up a VHS vs Beta Max.

@QuazarOmega @zeerooth

I don't understand why people do that. I am currently a cs student and I found that I spent more time using chatGPT than just doing things properly

@mihnt @[email protected] @just_another_person

I assumed that was the case. Yeah, I use his proton version as well.