home.social

#nixlang — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #nixlang, aggregated by home.social.

fetched live
  1. I think I finally found my gripe with nix

    So I've written code/configs in a fair number of languages, and most of them fall into three categories:

    • Bracy languages (C, Rust, Java)
    • Python/Lua/OCaml/Haskell (syntax wise, don't go on semantics)
    • lisps

    nix technically falls in the second

    but because attrsets are so pervasive, almost everything looks like the first

    Worst of all, even the arguments are deconstructed attrsets, so it's often just

    { a, b, c, ... } : { whatever }
    

    And my brain goes into bracy mode but I can't really use it because nix falls in the second category

    FAIR WARNING: I've only written nixos configs in nixlang so far. My gripes are with that. I don't really know how to define packages and such, so I can't tell you. I can probably write a flake, but that doesn't count.

    #nix #nixlang #nixos #programming #syntax #programminglanguages

  2. I think I finally found my gripe with nix

    So I've written code/configs in a fair number of languages, and most of them fall into three categories:

    - Bracy languages (C, Rust, Java)

    - Python/Lua/OCaml/Haskell (syntax wise, don't go on semantics)

    - lisps

    nix technically falls in the second

    but because attrsets are so pervasive, almost everything looks like the first

    Worst of all, even the arguments are deconstructed attrsets, so it's often just

    { a, b, c, ... } : { whatever }

    And my brain goes into bracy mode but I can't really use it because nix falls in the second category

    FAIR WARNING: I've only written nixos configs in nixlang so far. My gripes are with that

    #nix #nixlang #nixos #programming #syntax #programminglanguages

  3. I think I finally found my gripe with nix

    So I've written code/configs in a fair number of languages, and most of them fall into three categories:

    - Bracy languages (C, Rust, Java)

    - Python/Lua/OCaml/Haskell (syntax wise, don't go on semantics)

    - lisps

    nix technically falls in the second

    but because attrsets are so pervasive, almost everything looks like the first

    Worst of all, even the arguments are deconstructed attrsets, so it's often just

    { a, b, c, ... } : { whatever }

    And my brain goes into bracy mode but I can't really use it because nix falls in the second category

    FAIR WARNING: I've only written nixos configs in nixlang so far. My gripes are with that

    #nix #nixlang #nixos #programming #syntax #programminglanguages

  4. So I got this new (used) hardware at #gpn24 with a Intel i3 CPU at 3.7GHz, 2GB of RAM and 500GB of HDD. (two of those actually)

    And I am currently thinking about what to do with it.

    One "idea" (but it is absolutely insane) would be to use those two devices as VM hosts (libvirt for example), deploy a cluster of nixos VMs which run k8s to deploy stuff in k8s.

    Because #nixos you can do everything from above in plain #nixlang ... which is insane, but its also insane to do this with 2Gig of RAM hahaha.

    Another idea would be to just use them to test-deploy my pet project once it is in a state where you can deploy it.

  5. So I got this new (used) hardware at #gpn24 with a Intel i3 CPU at 3.7GHz, 2GB of RAM and 500GB of HDD. (two of those actually)

    And I am currently thinking about what to do with it.

    One "idea" (but it is absolutely insane) would be to use those two devices as VM hosts (libvirt for example), deploy a cluster of nixos VMs which run k8s to deploy stuff in k8s.

    Because #nixos you can do everything from above in plain #nixlang ... which is insane, but its also insane to do this with 2Gig of RAM hahaha.

    Another idea would be to just use them to test-deploy my pet project once it is in a state where you can deploy it.

  6. Not a bad read, but I accepted my fate that I'll die stupid without understanding why the declarative idea always bound to god-forsaken languages..
    And no, that crap does not look better than #nixlang imo..
    https://nemin.hu/guix.html

  7. Not a bad read, but I accepted my fate that I'll die stupid without understanding why the declarative idea always bound to god-forsaken languages..
    And no, that crap does not look better than #nixlang imo..
    https://nemin.hu/guix.html

  8. #Lix just merged an experimental integer coercion feature.

    That's useful if you want to interpolate an integer into a string. In #nixlang you previously needed to explicitly call `toString` to achieve that cast.

    And checking my personal configuration it looks like I can drop all `toString` usage in my configuration with this.

    git.lix.systems/lix-project/li

    #nixos #lix #nix

  9. #Lix just merged an experimental integer coercion feature.

    That's useful if you want to interpolate an integer into a string. In #nixlang you previously needed to explicitly call `toString` to achieve that cast.

    And checking my personal configuration it looks like I can drop all `toString` usage in my configuration with this.

    git.lix.systems/lix-project/li

    #nixos #lix #nix

  10. I'm not happy as a #NixOS user because of #NixLang but I'm finding I'm also not really happy as a former #Nix user either.

    Anybody want to give me the hard sell on #guix? Do you find the free software licensing requirement to be limiting? Is package availability a problem otherwise?

    Or should I give NixOS another shot?

  11. I'm not happy as a #NixOS user because of #NixLang but I'm finding I'm also not really happy as a former #Nix user either.

    Anybody want to give me the hard sell on #guix? Do you find the free software licensing requirement to be limiting? Is package availability a problem otherwise?

    Or should I give NixOS another shot?

  12. @skyr Da bist du in der heiligen Dreieinigkeit¹ des Nixiversums (hachyderm.io/@leftpaddotpy/111) falsch² abgebogen:

    #NixPkgs ist nicht #NixOS.
    #NixOS ist nicht die #NixDSL a.k.a. #NixLang.
    Die #NixDSL ist nicht #NixPkgs.
    (Und jeweils auch nicht umgekehrt)
    Aber alle drei¹ sind #Nix.


    ¹Den #NixPaketmanager/#NixInterpreter (#CppNix) gibts auch noch. «Viereinigkeit»? Mannigfaltigkeit?
    ²Wie so manche «falsche» Abzweigung kann auch das (über Umwege) zum Ziel führen. Und man lernt die Gegend besser kennen!

  13. @skyr Da bist du in der heiligen Dreieinigkeit¹ des Nixiversums (hachyderm.io/@leftpaddotpy/111) falsch² abgebogen:

    #NixPkgs ist nicht #NixOS.
    #NixOS ist nicht die #NixDSL a.k.a. #NixLang.
    Die #NixDSL ist nicht #NixPkgs.
    (Und jeweils auch nicht umgekehrt)
    Aber alle drei¹ sind #Nix.


    ¹Den #NixPaketmanager/#NixInterpreter (#CppNix) gibts auch noch. «Viereinigkeit»? Mannigfaltigkeit?
    ²Wie so manche «falsche» Abzweigung kann auch das (über Umwege) zum Ziel führen. Und man lernt die Gegend besser kennen!

  14. Kubernetes the Nix way parts 2 and 3 are out.

    Surprised even myself this evening with the API server and etcd up and working! This might not turn out to be a Sisyphean task after all!

    richtman.au/tags/k8s-nix-way/

    #Kubernetes #k8s #Nix #NixPkgs #NixOS #NixLang

  15. Kubernetes the Nix way parts 2 and 3 are out.

    Surprised even myself this evening with the API server and etcd up and working! This might not turn out to be a Sisyphean task after all!

    richtman.au/tags/k8s-nix-way/

    #Kubernetes #k8s #Nix #NixPkgs #NixOS #NixLang

  16. Times like this is when I wish Nix had `inherit` in lists (all the time)

    #nix #nixlang #nixos

  17. Now there's something you don't see every day.

    30-month contract in the French alps doing development of tooling to use Nix on supercomputers.

    recrutement.inria.fr/public/cl

    #Nix #NixLang #NixPkgs #NixOS

  18. Now there's something you don't see every day.

    30-month contract in the French alps doing development of tooling to use Nix on supercomputers.

    recrutement.inria.fr/public/cl

    #Nix #NixLang #NixPkgs #NixOS

  19. Give a man a flake, busy him for a day. Teach a man to nix, frustrate them for a lifetime.

    #Nix #NixLang #NixFlakes #NixOS #NixPkgs

  20. Give a man a flake, busy him for a day. Teach a man to nix, frustrate them for a lifetime.

    #Nix #NixLang #NixFlakes #NixOS #NixPkgs

  21. DevTooling effort: hey, you should try our new tool!
    Me: Is it docker or nix or a VM?
    DE: Haha, it's a good tool sir
    Look inside: nix

    #Nix #NixLang #NixPkgs

    @isabel

    akko.isabelroses.com/objects/3

  22. DevTooling effort: hey, you should try our new tool!
    Me: Is it docker or nix or a VM?
    DE: Haha, it's a good tool sir
    Look inside: nix

    #Nix #NixLang #NixPkgs

    @isabel

    akko.isabelroses.com/objects/3

  23. Love this cartoon but also would like to propose a motion that #nixLang and #NixOS folks rebrand to "nixologists" in the way that Rust folks are Rustaceans and Python folks are Pythonistas.

    theonion.com/teetotalitarianis

  24. Love this cartoon but also would like to propose a motion that #nixLang and #NixOS folks rebrand to "nixologists" in the way that Rust folks are Rustaceans and Python folks are Pythonistas.

    theonion.com/teetotalitarianis

  25. Hey so I'm restraining myself from just boosting all his posts, but if you're interested in the future of computing, I would definitely recommend following @jakehamilton. #aux (#auxOS?) looks like it's going to be a real thing and while I have my problems with #nixLang I really do think in 20 years all operating systems will be based on the foundational ideas of #NixOS.

  26. Hey so I'm restraining myself from just boosting all his posts, but if you're interested in the future of computing, I would definitely recommend following @jakehamilton. #aux (#auxOS?) looks like it's going to be a real thing and while I have my problems with #nixLang I really do think in 20 years all operating systems will be based on the foundational ideas of #NixOS.

  27. Congratulations @GabriellaG439 , the catgirl cover on this is both a mark of quality and ensures I won't be submitting a work spending approval for this 😹

    #NixOS #NixPkgs #Nix #NixLang

  28. Congratulations @GabriellaG439 , the catgirl cover on this is both a mark of quality and ensures I won't be submitting a work spending approval for this 😹

    #NixOS #NixPkgs #Nix #NixLang

  29. What's missing in the #NixOS community (from my perspective so far): documentation for the step from one host (relatively well documented) to multiple hosts with different configurations.

    There seems to be millions of possible ways to implement that and nothing seems to be documented.

    With one test notebook and one VM, I'm already totally lost since this really strange #nixlang (+ #flakes) requires weird magic spells for the simple tasks of defining host-specific includes. 😔

  30. My current issue with #nix, #nixOS and #HomeManager: I think I see their point how they solve some issues I'm facing. I may want to be there but I don't want to invest the energy to actually go there.

    Furthermore, there seems to be a chaotic-looking heap of concepts that are hard to initially understand and keep them apart.

    If I'd be in my twenties, I may have started with that ecosystem, embracing its style and concepts. 😔

    #nixlang #flake

  31. #Nix people, what's your approach to debugging? 🐛
    I often find I have to just make changes and try rebuilding to see if my fix is correct ❌. I know about the REPL but for something like a missing config option I'm not sure how to go about it.
    Any articles or blog links appreciated 🙏🏼

    The option `home' does not exist.

    github.com/arichtman/nix/tree/

    #NixLang

  32. CW: alcohol mention, de

    Was gibt es besseres als krassen #nixlang code zu hacken um seinen #rust build zu optimieren und dazu ein Glässchen Rotwein?

    Nur eins: Ne Mate dazu. Aber der Rotwein ist schon ein paar Tage offen und soll ja wohl nicht dzu Essig werden. Schwabenherz und so 💪