Multi-round Desktop Linux distribution showdown.
-
Come on NixOS, use your special powers to beat the Debian bully. You scrappy underdog you.
-
@rperezrosario I use NixOS and I'm still voting Debian lol.
This is a real question I ask myself every day. Kinda tempted to hop to Debian, but I maintain some nix stuff and its just so darn convenient to use nix.
I feel like Debian is a nice farm upstate that I will, eventually, retire to.
-
@rperezrosario I use NixOS and I'm still voting Debian lol.
This is a real question I ask myself every day. Kinda tempted to hop to Debian, but I maintain some nix stuff and its just so darn convenient to use nix.
I feel like Debian is a nice farm upstate that I will, eventually, retire to.
@abmurrow @rperezrosario I deal with debian packaging tooling at work, and the more I do so, the less I want to deal with debian in my own free time.
Nix and nix(pkgs) documentation are absolutely great compared to the mess around dpkg/apt/debhelper/lintian/different debhelper modules.
-
go, #nixos, go!
️ -
@rperezrosario Sorry, I’m old, and I like my computers boring.
-
@rperezrosario Neither, thank you
-
@abmurrow @rperezrosario I deal with debian packaging tooling at work, and the more I do so, the less I want to deal with debian in my own free time.
Nix and nix(pkgs) documentation are absolutely great compared to the mess around dpkg/apt/debhelper/lintian/different debhelper modules.
I tried nixOS back in 2023 and it was still too raw for me to use as my primary OS.
The nix scripting language also seemed a bit inelegant.
Then there was the matter of having any given application available as a nix(pkg).
Looking now, the website looks slick, and it looks like nixOS has matured and stabilized. So I am thinking of giving it another go.
What is your feeling on the current state of nix? Especially, the nix pkg selection?
-
I tried nixOS back in 2023 and it was still too raw for me to use as my primary OS.
The nix scripting language also seemed a bit inelegant.
Then there was the matter of having any given application available as a nix(pkg).
Looking now, the website looks slick, and it looks like nixOS has matured and stabilized. So I am thinking of giving it another go.
What is your feeling on the current state of nix? Especially, the nix pkg selection?
@purrperl @ar @abmurrow @rperezrosario
As a Nix user since 2020ish, package selection is bigger than ever, both literally in terms of having everything I want, and numerically; with more than Arch + AUR.
The language is largely unchanged, and the learning curve is still quite rough.
If you can get used to the language though it's a solid way to manage an OS though.
-
@purrperl @ar @abmurrow @rperezrosario
As a Nix user since 2020ish, package selection is bigger than ever, both literally in terms of having everything I want, and numerically; with more than Arch + AUR.
The language is largely unchanged, and the learning curve is still quite rough.
If you can get used to the language though it's a solid way to manage an OS though.
@purrperl @ar @abmurrow @rperezrosario
The best thing I can recommend if you decide to try Nix is find someone (like me as an example) who has been using Nix for a while, long enough to accidentally walk into the bear traps, and let them guide you through the woods.
-
I tried nixOS back in 2023 and it was still too raw for me to use as my primary OS.
The nix scripting language also seemed a bit inelegant.
Then there was the matter of having any given application available as a nix(pkg).
Looking now, the website looks slick, and it looks like nixOS has matured and stabilized. So I am thinking of giving it another go.
What is your feeling on the current state of nix? Especially, the nix pkg selection?
@purrperl @abmurrow @rperezrosario I've been using it since late 2019/early 2020, and - tbh - I didn't notice too many dramatic changes.
The nix language is still a somewhat weird functional programming language. The learning curve is a bit rough if you're not used to functional programming languages. REPL in the "official" implementation needs some love; one of the forks - Lix - mostly fixes REPL in my experience, and can be used on regular NixOS installations.
In my first few weeks/months of using NixOS i was treating
configuration.nixas just a silly json, with a slightly different syntax. I think that's a good approach to limit the number of things to learn at the same time.Flatpak and docker work on nixos, for the things that aren't packaged. AppImage sometimes need some work.
The number of packages in nixpkgs did grow.
-
@purrperl @abmurrow @rperezrosario I've been using it since late 2019/early 2020, and - tbh - I didn't notice too many dramatic changes.
The nix language is still a somewhat weird functional programming language. The learning curve is a bit rough if you're not used to functional programming languages. REPL in the "official" implementation needs some love; one of the forks - Lix - mostly fixes REPL in my experience, and can be used on regular NixOS installations.
In my first few weeks/months of using NixOS i was treating
configuration.nixas just a silly json, with a slightly different syntax. I think that's a good approach to limit the number of things to learn at the same time.Flatpak and docker work on nixos, for the things that aren't packaged. AppImage sometimes need some work.
The number of packages in nixpkgs did grow.
@ar @purrperl @abmurrow @rperezrosario I concur about treating it as silly json - Until you start doing conditionals and such you really can just treat it like that, and it's very effective.
Of course then you end up going down the flake based rabbit hole and end up like me with a configuration around 8000 lines long and covering give or take 5 different machines with varying degrees of difference - Laptop and Desktop are mostly the same, my router on the other hand...
(To be clear it's that complex because I enjoyed digging into it, not because it had to be.)
-
@purrperl @abmurrow @rperezrosario I've been using it since late 2019/early 2020, and - tbh - I didn't notice too many dramatic changes.
The nix language is still a somewhat weird functional programming language. The learning curve is a bit rough if you're not used to functional programming languages. REPL in the "official" implementation needs some love; one of the forks - Lix - mostly fixes REPL in my experience, and can be used on regular NixOS installations.
In my first few weeks/months of using NixOS i was treating
configuration.nixas just a silly json, with a slightly different syntax. I think that's a good approach to limit the number of things to learn at the same time.Flatpak and docker work on nixos, for the things that aren't packaged. AppImage sometimes need some work.
The number of packages in nixpkgs did grow.
Thanks for the thoughtful responses. I can probably get used to another quirky programming language, since I have worked with many other languages.
Might even look into writing a Ruby gem, or a Perl module, to implement a replacement to the nix language. Both Perl and Ruby are very flexible and user-friendly languages, and choosing either of those could significantly drive nixOS adoption.
-
Thanks for the thoughtful responses. I can probably get used to another quirky programming language, since I have worked with many other languages.
Might even look into writing a Ruby gem, or a Perl module, to implement a replacement to the nix language. Both Perl and Ruby are very flexible and user-friendly languages, and choosing either of those could significantly drive nixOS adoption.
@purrperl @ar @abmurrow @rperezrosario
Would that actually be... reasonable? I'm curious about your thoughts on how to implement it. -
Thanks for the thoughtful responses. I can probably get used to another quirky programming language, since I have worked with many other languages.
Might even look into writing a Ruby gem, or a Perl module, to implement a replacement to the nix language. Both Perl and Ruby are very flexible and user-friendly languages, and choosing either of those could significantly drive nixOS adoption.
@purrperl @abmurrow @rperezrosario I think you're underestimating the scope of "replace nix".
-
@purrperl @ar @abmurrow @rperezrosario
Would that actually be... reasonable? I'm curious about your thoughts on how to implement it.@krutonium @ar @abmurrow @rperezrosario
I'm speaking with very little knowledge here. I barely know the nix language. However, Ruby & Perl both lend themselves well to implementing Domain Specific Languages.
-
@abmurrow @rperezrosario I deal with debian packaging tooling at work, and the more I do so, the less I want to deal with debian in my own free time.
Nix and nix(pkgs) documentation are absolutely great compared to the mess around dpkg/apt/debhelper/lintian/different debhelper modules.
@ar @abmurrow @rperezrosario
The NixOS community strife pretty much put me off the project entirely. I don't know if it's been resolved at this point, but, regardless, the damage has been done. -
@krutonium @ar @abmurrow @rperezrosario
I'm speaking with very little knowledge here. I barely know the nix language. However, Ruby & Perl both lend themselves well to implementing Domain Specific Languages.
@purrperl @ar @abmurrow @rperezrosario I'm not sure how cleanly you could do it, considering a number of factors like the entirety of nixpkgs also being implemented as nix, and it being a functional language, which I'm relatively sure (I've never used them) Ruby & Pearl are not, which is going to cause a lot of issues on it's own.
That said, don't let me stop you, I do not know a lot about this problem domain.
But bare minimum I think you'd end up having to implement the nix language as well as your own DSL. Or have your code transpile to Nix maybe?
-
@purrperl @abmurrow @rperezrosario I think you're underestimating the scope of "replace nix".
Indeed, I am. However, I am launching a Free Software co-operative, and will actually hire other programmers and collaborate with them on something this ambitious in scope.
Here's the work-in-progress of the co-operative vision statement. Please feel free to send suggestions and pull requests.
-
@purrperl @ar @abmurrow @rperezrosario I'm not sure how cleanly you could do it, considering a number of factors like the entirety of nixpkgs also being implemented as nix, and it being a functional language, which I'm relatively sure (I've never used them) Ruby & Pearl are not, which is going to cause a lot of issues on it's own.
That said, don't let me stop you, I do not know a lot about this problem domain.
But bare minimum I think you'd end up having to implement the nix language as well as your own DSL. Or have your code transpile to Nix maybe?
@krutonium @ar @abmurrow @rperezrosario
Perl & Ruby are both multi-paradigm languages, and the functional programming paradigm is well-supported by both, in addition to OOP.
-
@krutonium @ar @abmurrow @rperezrosario
Perl & Ruby are both multi-paradigm languages, and the functional programming paradigm is well-supported by both, in addition to OOP.
@purrperl @ar @abmurrow @rperezrosario
Good to know!
I've never had an opportunity to use them, and now I kinda want to go read about this.
