nix-documentation.txt

Design the website interface as layers and people can opt in what to include for example a terminology layer where every single nicks term is linked to the glossary there's also another layer would link every single command and function reference to the function reference and so on. There could be a goof layer there you could link to my quote funny things on quote
Oct 15 10:49am

> How exactly, command by command, would nix solve the same problems? This might... | Hacker News
news.ycombinator.com
https://news.ycombinator.com/item?id=26749676
Oct 15 10:50am
https://news.ycombinator.com/item?id=26750386
Oct 15 10:52am

Right, I do not disagree with a tutorial that outlines Nix in this way. Indeed, ... | Hacker News
news.ycombinator.com
https://news.ycombinator.com/item?id=26750864

I think step by step guides would work if it also explains the terms and concepts in question along with the commands commands may change but not the concepts or more rarely
Oct 15 10:56am
However this would make it such tutorials redundant with the central text so either accept that redundancy in a single body of text or create a separate section of tutorials running alongside the central text in parallel but yet still redundant maybe reference to the central text and back and forth
Oct 15 10:57am
> All of these are good ideas in my opinion. Nix needs better documentation, but the answer isn't more "build production on Nix in 5 minutes" guides, but more "go on an adventure to understand Nix thoroughly and make using it obvious" guides, IMO.

So the game idea is good:)
Oct 15 11:00am

So nix is kind of weird thing, because parts of it you can use to replace part o... | Hacker News
news.ycombinator.com
https://news.ycombinator.com/item?id=26759534
Oct 15 11:50am
RFC for consistent package naming? https://news.ycombinator.com/item?id=26751238
Oct 15 1:20pm
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
Oct 15 1:25pm
"there are different kinds of nix expressions" https://news.ycombinator.com/item?id=26752991
Oct 15 2:18pm

Thumbnail link preview for www.reddit.com
Node packages installed by nix have incorrect permissions
No, I don't have blog, maybe I should. But here is an example of a full setup, of course you can customize it. For example instead of using niv...
www.reddit.com
https://www.reddit.com/r/NixOS/comments/nk1fdy/comment/hgrnury/?%24deep_link=true&correlation_id=26dab63b-06a6-4e9a-b4be-79b13bb8add0&ref=email_comment_reply&ref_campaign=email_comment_reply&ref_source=email&utm_medium=Email%20Amazon%20SES&%243p=e_as&_branch_match_id=7729516137559100084
Oct 15 2:24pm
https://news.ycombinator.com/item?id=26749652
Oct 16 11:45am
Questions above
Oct 16 11:45am

You
Design the website interface as layers and people can opt in what to include for example a terminology layer where every single nicks term is linked to the glossary there's also another layer would link every single command and function reference to the function reference and so on. There could be a goof layer there you could link to my quote funny things on quote
Another layer could be to show the author's notes for example my fixation with the fixed point and why I find it so difficult to understand
Oct 17 11:12am
https://www.youtube.com/watch?v=aydaRkcbC_A
-> from 10:30: distinguishes build inputs and dependendencies, and gives examples of non-source code input! (in this case, research data, that still needs to be fetched
-> 13:50 - explains succinctly what a derivation ("a recipe for producing a build product that captures all its inputs and the actions required to produce the output")
Oct 18 1:05pm

How does Nix build stuff? Sounds stupid but still struggling with this question. I probably totally missed the point every time I started out with Nix, but it seems that there is no docs out there that are centered around the "building stuff" part that Nix "just" facilitates in a more reproducible manner.

This is my understanding:

Nix is a framework that manages the the build inputs and outputs (isolate by hashing, etc.), the DAG, etc. but the actual build is always done by external "builders", where "builder" stands for compiler (in very simple cases) or build systems such as make, rebar3, mix, etc. that eventually compile stuff but they also add extra functionality (ensure code organization, etc.)

QUESTION: Isn't Nix lang using make (and similar) are duplication of efforts, impure, etc.? My understanding is that Nix takes the global view of "package management" whereas build tools such as make create the packages. Is this the right way to think about it?
-> TODO: !!! look at https://www.boronine.com/2018/02/02/Nix/

TODO: Look into how lang-specific builds work. E.g., Erlang's rebar3 has a Nix function, which is kind of like make (or exactly like it?): organizes files the way the BEAM expects it, compiles sources via erlc, and voila.So the "output" is going to be the built project is the Nix store under a separate hash, right?

BEAM lang ideas

• https://elixirforum.com/t/how-to-make-an-elixir-library-available-to-erlang-users/5172 -> what if Nix would be the package manager for every BEAM based lang (see https://elixirforum.com/search?q=nix and the entire nix-beam bookmarks folder) (this is probably re-inventing the wheel, and it is already tried/in use/etc. I just don't understand Nix enough yet)