←back to thread

Trying Guix: A Nixer's impressions

(tazj.in)
194 points todsacerdoti | 1 comments | 15 Jul 25 08:11 UTC | HN request time: 0.001s | source
Show context
idlip ◴[15 Jul 25 17:11 UTC] No.44573461[source]▶
Its nice read. We need more of comparative posts by user familiar with both nix and guix.

We see bias with most discussions.

Only cons with Guix I see is, lack of infrastructure and less volunteers to work on guix eco-system. If its solved, I can imagine guix can improve exponentially.

replies(4): >>44607020 #>>44607098 #>>44608492 #>>44609855 #
tempfile ◴[18 Jul 25 17:00 UTC] No.44607098[source]▶
The major con is in the article, it is super slow to update. Half an hour is just crazy, nobody will move to that if they know.
replies(7): >>44607183 #>>44607656 #>>44607956 #>>44608088 #>>44608768 #>>44613046 #>>44614065 #
1. kwk1 ◴[18 Jul 25 17:41 UTC] No.44607656[source]▶
It doesn't usually take that long, but the first `guix pull` is quite slow, and what should be a no-op of running it a second time immediately afterwards also takes too long.

Edit: Just to provide a measurement, on my Framework 13 with AMD Ryzen 5 7640U, a `guix pull` which pulled in 1 nonguix commit and 64 guix commits took 2m10s, and a subsequent no-op `guix pull` took 1m18s.