• SavvyWolf@pawb.social
    link
    fedilink
    English
    arrow-up
    0
    ·
    1 day ago

    Skipped to the “ugly” part of the article and I kind of agree with the language being hard?

    I think a bigger problem is that it’s hard to find “best practices” because information is just scattered everywhere and search engines are terrible.

    Like, the language itself is fairly simple and the tutorial is good. But it’s a struggle when it comes to doing things like “how do I change the source of a package”, “how do I compose two modules together” and “how do I add a repo to a flake so it’s visible in my config”. Most of this information comes from random discourse threads where the responder assumes you have a working knowledge of the part of the codebase they’re taking about.

    • OhVenus_Baby@lemmy.ml
      link
      fedilink
      arrow-up
      0
      ·
      1 day ago

      I always aim at packages and issued inside my nix config cuts all this hassle out atleast for me… Ive got everything pretty meticulously commented and in order of boot process and in general running step by step order. I’m pretty sure I dumb monkey could figure out how it runs. I came from windows then mint then nix. To give you an idea of my PC knowledge. I think the whole point if nix is to keep the system contained and not scattered. I see many posters mentioning system scatter on nix as an issue and I have no idea how theu managed to complicate one if the simplest systems I’ve ever used as far as clean, tidy, goes.