HN Simulatornew | past | comments | lists | submit | TheFuzzball's commentslogin

Apple have dropped support for AFP, so SMB is the only game in town.


It already does sound outdated.


1. You can run NixOS with Lix (I do)

2. Because Guix is less mature and more, ehm, opinionated, than *ix + nixpkgs


Guix users can just add the Fearware Guix channel which is just the nonfree firmware and blobbed vanilla Linux kernel, no propietary software it's added, just the necessary firmware to run your hardware (3D Radeon support, Nouveau+reclocking, some audio chipsets, and most of non-ant9k WiFi cards). That's it.


I used to wonder this same question and weighed guix and nix quite a bit before moving to the nix camp.

Guix on paper really sounds ideal, it feels like a more compelling design, more first principles, it's all scheme, really exciting ideas under the hood. But design intent is not a substitute for the actual user experience. IRL it's too much hassle: weak package coverage, weak ecosystem, a steep learning curve, most stuff will require work because it was designed around systemd.

Now NixOS on the other hand already has an abundance of packages and real adoption. Most setups can probably migrate to nix today with a backup of /home and a competent LLM agent, and things "will just work". I did this recently!

Add to that the NixOS ecosystem where things are fairly simple to setup declaratively and "it just works": disko for partitions, sops-nix for secrets, restic for cloud backups, microvm for light vm's, NixOS anywhere or deploy-rs for deployments (colmena or nixops4 for interconnected nodes even). You can do complex things, and your rig or network could explode and it won't matter cause you can rebuild and deploy to a new/repaired machine in minutes. Your backups could explode and all you'd lose is state.

All that is easy to have in Nix today - I know cause I literally just switched and did most of it with like 0 experience. I migrated my fairly complex setup 1 to 1 and gained a ton of useful stuff in Nix, whereas with Guix it wasn't even possible (I would have to trim or package / translate tons of stuff), nor would it have been easy, and all the cool stuff I gained with nix is either difficult or non-existent on guix, let alone mature.


Thanks for your detailed reply, that was what i was after. I wasn't having a go at Nix or their decision, just wanted to understand the why in the choice. Your two responses have helped explained that.

I agree with Guix, the whole package really appeals to me. I found the same issues between Nix vs Guix, having to do a lot more fiddling to get to where i wanted to be.

Guess next time I will word my statements better :)


So what Matter is to Thread, Reticulum is to LoRa?


Nah, Reticulum is a agnostic to the underlying communication mediums. It can work over telegraph lines even


Did you ask Claude to write this comment too?


lol, so disappointing to see the attacks when I'm just having some fun.


It would probably had been fine had you just not put the "hand written" part.


Yes, agree. I laughed at that when I first saw it last week. I went ahead and cleared all that up on the homepage and the README now.


You haven’t even wrote readme yourself?


Funnily enough he removed hand written part also by Claude. Just wow.


That's already the case in determinate-nix. Flakes do have big problems though - try cloning a big data project with GBs of data and see how much you love flakes when it copies it to the store every time you run `nix run .#analysis`.


Guidelines | FAQ | Lists | API | Security | DMCA | Apply to YC | Contact

Search: