3 ms·
> for some reason it never tells you what the point of all of this is, so I think many folks might feel turned off by it I’m attempting to write some hands-on
by lloeki 6y ago
> for some reason it never tells you what the point of all of this is, so I think many folks might feel turned off by it
I’m attempting to write some hands-on pragmatic no-bullshit articles tackling that.
Why? I’ve been hearing a lot about Nix over the years, how it’s an experiment yet so good it’s actually usable. But every article I found obscure the good parts, either because of too much details and theory or because they’re apt->nix-env but without the whys.
And the good parts are really good. So good that as soon as I was enlightened I simply dropped my lonesome 13 years ArchMac project on the floor.
But it needs a pragmatic approach to explaining what it is and how it can be of value to you day to day. Everything is actually in the manual, but it lacks some ties with existing knowledge for people to make the jump, unless they’re really really curious enough to piece things together.
That’s what I’m writing.
- takeda 6y agoThat sounds great. I remeber when I started, it was very difficult, I don't think I would be able to start without nix-pills articles. Nix needs more tutorials, especially in areas that could showcase it (which you planning to do). Nix is often referred as a package manager, but I believe that characterization does a bit of disservice to it, because it can do much more than that. IMO the areas where it excels the most for me is the build system. Ability to have a language define the exact environment that developer has is IMO awesome.