It wasn't for nothing
gexp.no
It wasn't for nothing
1–10 of 165 posts
Re: It wasn't for nothing
#2Re: It wasn't for nothing
#3this is actually awesome
Re: It wasn't for nothing
#4Re: It wasn't for nothing
#5Re: It wasn't for nothing
#6Re: It wasn't for nothing
#7I'm not a developer but I totally relate to this. Most of my creative pursuits are weird, niche, sometimes avant-garde. If I didn't make my artifacts, nobody else would, and it is so intrinsically rewarding to see my visions instantiated, even if they pale in comparison to my first imagining of what they might be. Because I have fringe-y interests, most people don't necessarily "get" it. (Probably true of everyone el…
Re: It wasn't for nothing
#8I'd love to know how the authors financials work. It sounds like a dream to work on something just because it's fun and fulfilling. I have mouths to feed and that dominates much of my career choices. I'm in a small town in a small country so earning a FAANG salary is not an option. I can't save up and go work on a dream project.
Re: It wasn't for nothing
#9After using and contributing NixOS for 3 years, I appreciated that I understood far more how Guix worked after just one 1-2 weeks of using it.
Guix introduces abstractions, such as operating-system that has defined fields that make it clearer what structures are being built. NixOS, on the other hand, does not have such abstractions (or perhaps just not as well documented/discoverable).
Alas, I found Guix a bit slow and a bit difficult to contribute to (mailing list workflow, and fewer reviewers), and don't have the capacity to help improve that, and so I'm back to NixOS.
Guix is tackling multiple fronts: a blob-free kernel, a non systemd init, mailing list development, bootstrapability, no non-free software, high standards for commit messages.
If they reduced the number of fronts they were tackling, they might increase contributions, but the current contributors seem to value their existing fronts. That's fair.