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

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.

back when i was first learning #nixlang everybody online told me it was basically "JSON but with functions" and now that i'm taking a programming paradigms class and we've gotten to the functional programming chapter, i gotta say, that was a really really weird way to spell "#Haskell but with about half the features missing"

i love thinking i'm stupid for not immediately understanding functional programming concepts without being told that's what i'm learning

#nix #nixos

Which is worse hell to write?

Evaluate on criteria such as lack of usable documentation, code ugliness, ease of determining what is wrong when something won't work, and generally the amount of headaches you experience trying to get something to work

#rust #rustlang #nix #nixlang #nixos

Join us for NixOS CN Meetup #1 on August 9–10 held at ShanghaiTech University’s Pudong Campus, the first-ever Nix-focused event in China!

https://discourse.nixos.org/t/first-ever-nixos-cn-meetup-2025-08-09-10-shanghai/67457

#nixos #nixlang #meetups

#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.

https://git.lix.systems/lix-project/lix/src/branch/main/doc/manual/rl-next/integer-coercion.md

#nixos #lix #nix

How we use Nix with Flakes ❄❄❄❄

https://qeef.srht.site/post/how-we-use-nix-with-flakes/

It looks like we use Nix with flakes since cradle to the grave.

Considering Nix flakes being experimental, that’s scary.

And Nix laungage itself does not help, neither so many conventions and confusions one needs to keep in mind.

#Nix #NixLang #NixFlakes

You can write nicer nix code

https://qeef.srht.site/post/you-can-write-nicer-nix-code/

Here are some suggestions:
- Make nesting match the scope.
- Name things and name them properly.
- Let things in `let ... in ...` follow order.

#Nix #NixLang

Warning! Nix language!

https://qeef.srht.site/post/warning-nix-language/

I wrote a piece. But I am too tired to read it after myself. Sorry.

#Nix #NixLang