this post was submitted on 09 Apr 2024
214 points (95.0% liked)
Linux
47950 readers
2108 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
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I've been messing about with NixOS for the past 2 weeks or so. While I think I know enough to plug in the right text in the right spots to get a system configured I feel like I understand nothing about the nix language and the syntax is extremely unintuitive to me. If another distro offered declarative configuration as well as something like Nix's options I would easily swap away from NixOS at this point.
Pure lazy unityped lambda calculus, basically a lazy lisp with records instead of lists. Or a pure, lazy, lua.
Pure is important because reproducibility, lazy is important to not have to evaluate all of nixpkgs before you can build anything, lambda calculus well it needs to be turing complete, support things like functions in in some way though TC is only used very, very very deep down in the system. They literally use the y-combinator to do recursion, like when bootstrapping stdenv.
The syntax is unintuitive, yes, but aside from the semicolon cancer actually not that bad. My biggest gripe with the language is it not having a proper type system, like you put a list where a string is expected or the other way around and you get five screenfuls of backtrace through the whole evaluation stack and due to laziness the actual location of the error might not even be in there.
A replacement is actually already in the pipeline.