For an amazing fighting game guide/tutorial I can't recommend https://ki.infil.net enough. Its centered around Killer Instinct but describes general fighting game concepts really well. It has really great visuals/inline videos

While nix can be very intimidating to get going, I think for just getting developer environments spun up it can be somewhat simple. I highly reccomend trying to add a `flake.nix` to your projects. It makes on boaring new devs a breeze https://medium.com/immuta-engineering/nix-and-skaffold-for-p...

Yea I think the main issue holding nix back is lack of documentation/standards on how to do things.

Like the other commenter mentioned how npmlock2nix exists but it's hard to figure out that these tools exists.

Im hoping that flakes help solve alot of problems to make it easier for users to jump in. Then hopefully the documentation problem will naturally start going away as more people start using nix.

From the 2022 Nix Survey's results: https://discourse.nixos.org/t/2022-nix-survey-results/18983

The main pain points people identified:

- Getting started with Nix is hard.

- The documentation isn't great for getting started, for getting some task done, and is spread across many places.

- Debugging bad Nix code is hard.

- Contributing back to Nix is hard.

Despite the above, I think most of the respondents had just started using Nix within the last year or two.

I think some of the Summer of Nix effort is towards improving documentation. e.g. https://discourse.nixos.org/t/summer-of-nix-documentation-st...

Bad or missing documentation on Nix is a known issue. I think a big part of this issue is that the language itself doesn't have a mechanism to provide documentation.

Python has docstrings, Java has javadoc, Hare has haredoc, Lua has emmylua... etc. Every language has SOME WAY of leaving explanation on what a function does, and what values it takes. Nix doesn't seem to have such a thing (if it does, it's a well-kept secret!).

Functions being lazy doesn't help, since that makes it very hard for tools to provide feedback without actually executing the right codepaths. And finding the definition of a function is HARD.

It sort of does for modules [1] but not functions iirc.

[1] https://nixos.wiki/wiki/Declaration

Not sure why I always forget amend exists. That is much cleaner

Yea I will agree it's daunting. I've been using nix os for 2 years and this was my first time making a pr back.

I think using nix for personal projects helps build your mental model a lot more. Once you take the time to build a package manually alot of it clicks.

As a user of nixos/nix if you're not building packages it's great. Nixos is quite declarative for most settings. The main issue is just figuring out what options exist...

Nix as a home brew replacement without using homemanger/nix Darwin is not a great sell to me imo.

Using flakes and using it for project dependencies though is amazing and quite easy to use imo.

We decided to use it at my job for a new project and it's been pretty amazing https://link.medium.com/DwIGVmRZ6rb