A🐝

Guix Survey Results P1.

Few user comments I really agree with...

  • Lack of drivers within the distribution
  • Unavailable proprietary software
  • Free Software as a constraint
  • Old-fashioned communications

(note: telling people about nonGuix in the main doc/adding to the installer would be a great start to some of those points above).

I screen-shotted the communications one because it's been one of my sore points in trying to keep track of what’s going on behind the scenes.

Dowloading .mbox to read old emails or using the online email archive page didn't make for a conducive experience. Don't get me started about the patch download routine. Who even gets taught that these days.

Guix User and Contributor Survey 2024: The Results (part 1) — 2025 — Blog — GNU Guix

Blog posts about GNU Guix.

Jan 16, 2025 at 11:44amWeb
Show threadA🐝Jan 24, 2025

Guix Survey Results P2.

This section of the results echos part of the first one. Though there are a few things I want to pull out from it.

On Table 14: Proprietary driver usage, 20% didn't use proprietary drivers, 66% used Nonguix and 49% used proprietary on foreign distros.

Those numbers are much higher then I had guessed. Maybe an open discussion can be had about mentioning Nonguix in the docs, given it's prevalence.

On Table 17: Guix user satisfaction limiters. 48% have an issue with Guix runtime performance. 39% on Error messages and debugging.

That's two areas I'd love to see more on solving. But they're unlikely to be easy fixes either.

Guix User and Contributor Survey 2024: The Results (part 2) — 2025 — Blog — GNU Guix

Blog posts about GNU Guix.

Show threads_levi_sJan 17, 2025
@MinervasRefuge Exactly. Just searched for 'Guix' to see if someone already commented exactly on that point :D Guix really should switch to a "modern" communication workflow e.g. with forgejo and something like a zulip or discourse forum imo