For example, I’m using Debian, and I think we could learn a thing or two from Mint about how to make it “friendlier” for new users. I often see Mint recommended to new users, but rarely Debian, which has a goal to be “the universal operating system”.
I also think we could learn website design from… looks at notes …everyone else.
Give me immutable, declarative Arch.
NixOS on your mind too? lol
Yep
I think that’s what BlendOS is working towards. You might keep an eye on them.
Oh nice. This looks promising. I’m guessing it’s not totally ready yet?
It may be ready, I haven’t tried their latest version. Most of the functionality was there, but it had some rough spots. I’ve been meaning to go back and try daily driving it again.
What do you miss in NixOS (Unstable)?
I think a declarative, atomic LTS distro (e.g. Alma) would be quite nice for business use.
I gather that not everything is compatible with nixOS, and it’s better as a server than for development or as a general OS.
I didn’t know Alma was declarative.
Makes sense.
No, I wish for something like Alma, but declarative and atomic :)
It’s something we might see with the next EL release cycle.
rpm-ostreehas treefiles complete with the option for (experimental) lockfiles. There’s already config files for CentOS Stream to build CentOS Stream CoreOS, and those can be adapted for Alma. I think, atm, it’s more of an issue of general interest than technical limitations.Ah nice, thanks for pointing me to it!
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.