NixOS Marketing | 266 Members | |
| NixOS website + marketing team: https://nixos.org/community/teams/marketing.html | 58 Servers |
| Sender | Message | Time |
|---|---|---|
| 30 Apr 2024 | ||
| 22:23:22 | ||
| 1 May 2024 | ||
| garbas: IdaBzo: Now this is some news to post! https://discourse.nixos.org/t/nixos-foundation-board-giving-power-to-the-community/44552 | 03:09:11 | |
| Hey team I've made some progress on the official Nix cheat sheet. Looking for some initial feedback. Preview in thread. | 05:06:12 | |
Download image.png | 05:06:25 | |
| djacu Nothing other than that looking absolutely dope! | 07:40:31 | |
| djacu Oh here's something else: inherit doesn't alway desugar to x = x | 07:42:11 | |
| E.g. `x: rec { inherit x; }` | 07:43:33 | |
| cool! the 'bind set arguments' (top-right) can't decide between 'set' or 'args' it seems? | 07:51:27 | |
| maybe use 'attribute set' rather than just 'set' in that description? ('set' may invoke different expectations to people not familiar with nix) | 07:52:43 | |
| * cool! the 'bind set arguments' (bottom-right) can't decide between 'set' or 'args' it seems? | 07:53:12 | |
| djacu Also "update" attribute sets instead of "merge". Merge sounds recursive | 08:03:44 | |
| djacu Actually maybe it's best to just post it in a Nix issue so that the Nix team can briefly bikeshed and check it? :P | 08:05:04 | |
| It looks really cool though, let's get that posted soon! | 08:05:26 | |
| Perhaps a mention that builtins exist? A full pverview is out of scope, but it might be good to point out. | 08:47:55 | |
| * Perhaps a mention that builtins exist? A full overview is out of scope, but it might be good to point out. | 08:48:10 | |
| good point, maybe point to 'further references' like https://nixos.org/manual/nix/stable/language/builtins.html and https://nixos.org/manual/nixpkgs/unstable/#id-1.4 ? Getting hard to fit in, though, I can imagine ;) | 09:07:40 | |
| 15:06:50 | ||
In reply to @raboof:matrix.orgYeah ideally I would use 'attribute set' here but it didn't fit on a single line. Space is a premium so I shortened it to set. Thinking about just removing the word 'set` here. Since it is a continuation from the previous three examples, it should be clear that it is still an attrset | 15:11:05 | |
In reply to @raboof:matrix.org The inspiration was the nixcademy cheat sheet. I changed the bind arguments variable to | 15:13:17 | |
| Wow thanks for all the feedback everyone. For reference, we are trying to emulate something similar to the nixcademy cheat sheet (https://nixcademy.com/cheatsheet.html). This one being just for the nix language. The design goals I am working with are
We could go to 2 pages but ideally it would be 1 for the nix language and 1 for nix commands. | 15:20:26 | |
| Doesn't it still hold true in this case?
| 15:28:54 | |
| Makes sense, then it should be 'args.x' and 'args.y' right? | 15:29:44 | |
In reply to @raboof:matrix.orgWe really need to get our own URL shortener | 15:31:04 | |
| ah yes i see what you mean. i caught that right after i posted it last night. forgot to mention it. thanks for calling it out! | 16:20:27 | |
| 2 May 2024 | ||
| I searched about the following keywords online but didn’t find anything compelling. Did we ever market/talk about the whole Nix ecosystem as an artifact builder? In my limited experience trying to spread Nix love at work, I was originally faced with push backs because ppl were thinking of Nix as a competitor to docker because docker can do things that nix do: ppl use docker to setup dev environments, docker containers (duh) and has thus overlap with Nix that made it not obvious how Nix fit in. But then I switched to first explaining Nix as an artifact builder. And everything flows naturally from that. I then explain the sandboxing and how that relates to inputs and output and the hashing. Since this sandboxing goes all the way down, we can build a full BoM up to the exact commit of the shell used to build the Go compiler (we’re essentially a Go shop) that we use to compile our binary. Then I introduce that Nix has fine grained caching so we don’t need to rebuild the world each time. That ppl then realized it can build binaries but also config files, systemd services, ISOs, wholes OSes and docker containers. This means the dev environment has the exact same packages as the docker container which eliminates one of our frustrations at work. And that this includes all dependencies since it can package anything. I can continue forever so I’ll stop here but I just wanted to share this - currently in its early infancy - approach I’m using to explain Nix and everyone - literally everyone - I talked to see a great appeal to it that way. IMO this fits nicely in our work environment because it fixes our dev env which is in need of love but no one likes to take care of. | 01:26:51 | |
| * I searched about the following keywords online but didn’t find anything compelling. Did we ever market/talk about the whole Nix ecosystem as an artifact builder? In my limited experience trying to spread Nix love at work, I was originally faced with push backs because ppl were thinking of Nix as a competitor to docker because docker can do things that nix do: ppl use docker to setup dev environments, docker containers (duh) and has thus overlap with Nix that made it not obvious how Nix fit in. But then I switched to first explaining Nix as an artifact builder. And everything flows naturally from that. I then explain the sandboxing and how that relates to inputs and output and the hashing. Since this sandboxing goes all the way down, we can build a full BoM up to the exact commit of the shell used to build the Go compiler (we’re essentially a Go shop) that we use to compile our binary. Then I introduce that Nix has fine grained caching so we don’t need to rebuild the world each time. That ppl then realized it can build binaries but also config files, systemd services, ISOs, wholes OSes and docker containers. This means the dev environment has the exact same packages as the docker container which eliminates one of our frustrations at work. And that this includes all dependencies since it can package anything. I can continue forever so I’ll stop here but I just wanted to share this - currently in its early infancy - approach I’m using to explain Nix and everyone - literally everyone - I talked to see a great appeal to it that way and seem to understand how Nix and nixpkgs and NixOS all fit together. At least this fits nicely in our work environment because it fixes our dev env which is in need of love but no one likes to take care of. | 01:29:10 | |
| * I searched about the following keywords online but didn’t find anything compelling. Did we ever market/talk about the whole Nix ecosystem as an artifact builder? In my limited experience trying to spread Nix love at work, I was originally faced with push backs because ppl were thinking of Nix as a competitor to docker because docker can do things that nix do: ppl use docker to setup dev environments, docker containers (duh) and has thus overlap with Nix that made it not obvious how Nix fit in. But then I switched to first explaining Nix as an artifact builder. And everything flows naturally from that. I then explain the sandboxing and how that relates to inputs and output and the hashing. Since this sandboxing goes all the way down, we can build a full BoM up to the exact commit of the shell used to build the Go compiler (we’re essentially a Go shop) that we use to compile our binary. Then I introduce that Nix has fine grained caching so we don’t need to rebuild the world each time. That ppl then realized it can build binaries but also config files, systemd services, ISOs, wholes OSes and docker containers. This means the dev environment has the exact same packages as the docker container which eliminates one of our frustrations at work. And that this includes all dependencies since it can package anything. Which solves a second pain we have which is bootstrapping a new engineer’s laptop. I can continue forever so I’ll stop here but I just wanted to share this - currently in its early infancy - approach I’m using to explain Nix and everyone - literally everyone - I talked to see a great appeal to it that way and seem to understand how Nix and nixpkgs and NixOS all fit together. At least this fits nicely in our work environment because it fixes our dev env which is in need of love but no one likes to take care of. | 01:36:10 | |
| Yes! I've used a very similar flow to help describe Nix. I usually add the term "... with very good bookkeeping". | 03:17:27 | |
| 3 May 2024 | ||
An old mention of 80 000 packages was forgotten in NixOS webpage, I just made a pr to updatehttps://github.com/NixOS/nixos-homepage/pull/1414 | 03:22:27 | |
| Thanks! | 03:33:41 | |