this post was submitted on 18 Feb 2024
129 points (93.9% liked)

Linux

48352 readers
521 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago
MODERATORS
 

Distro agnostic packages like flatpaks and appimages have become extremely popular over the past few years, yet they seem to get a lot of dirt thrown on them because they are super bloated (since they bring all their dependencies with them).

NixPkgs are also distro agnostic, but they are about as light as regular system packages (.deb/.rpm/.PKG) all the while having an impressive 80 000 packages in their repos.

I don't get why more people aren't using them, sure they do need some tweaking but so do flatpaks, my main theory is that there are no graphical installer for them and the CLI installer is lacking (no progress bar, no ETA, strange syntax) I'm also scared that there is a downside to them I dont know about.

(page 2) 50 comments
sorted by: hot top controversial new old
[–] cybersandwich 3 points 9 months ago

Nix is the vim of package management but without good documentation. So it's incredibly powerful and useful once you get into it, but imagine trying to learn vim without any docs or guidance. Vim has a steep learning curve with good documentation, YouTube tutorials, blog posts, and forum guides.

Nix doesn't really have a wealth of that.

That's nix package management and nixos in a nutshell.

[–] [email protected] 2 points 9 months ago (8 children)

How does it solve the problem of dependencies without becoming bloated?

[–] clemdemort 3 points 9 months ago

From what I gather it goes something like this:

  • every package is assigned a hash
  • every package lists their dependencies through their hashes
  • different versions of packages have different hashes
  • when you launch an application it creates an environment with all its dependencies, this means that two applications that both use the same library at the same version share that library. However if they both require the same lib but not the same version of that lib they don't share it.

Which solves DLL hell as far as i understand it.

load more comments (7 replies)
[–] BigTrout75 2 points 9 months ago (1 children)

Steam Deck is using Flatpaks so.....

load more comments (1 replies)
[–] ChonkaLoo 2 points 9 months ago (1 children)

Was curious myself don't like flatpaks & appimages much, but from a quick googling, they don't seem to integrate with the desktop so you need to launch them from terminal? That is a deal breaker for me at least.

[–] clemdemort 3 points 9 months ago* (last edited 9 months ago) (1 children)

you have to set up the XDG_DATA_DIRS environment variable to take into account ~/.nix-profile/share the desktop icons will only appear after a relogin though.

[–] [email protected] 1 points 9 months ago

It's automatically set up alongside PATH

[–] [email protected] 2 points 9 months ago

My guess would be that it's because Flatpaks are easy. You have a handy GUI tool often pre installed that includes search and one-click install.

If you want something lower level, Arch users have the AUR, and others may actually do that horrifying curl https://... | sh pattern.

Nix pancakes on the other hand.... I have no idea how to use them and generally assume it's the thing NixOS uses. Since I don't use NixOS, I've never given them a second thought.

load more comments
view more: ‹ prev next ›