NixOS Marketing - Public Room Timeline

	NixOS Marketing	266 Members
	NixOS website + marketing team: https://nixos.org/community/teams/marketing.html	57 Servers

Load older messages

Sender	Message	Time
1 May 2024
djacu	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
ibizaman	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
ibizaman	* 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
ibizaman	* 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
tomberek	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
Sigmanificient	An old mention of `80 000 packages` was forgotten in NixOS webpage, I just made a pr to update https://github.com/NixOS/nixos-homepage/pull/1414	03:22:27
tomberek	Thanks!	03:33:41
ibizaman	I'm being overly pedantic here on purpose so feel free to push back. With that in mind: For Path, change to Path with context? Or string with context? This would give ppl a keyword to search for in the let ... in example, isn't there too many times the word "return"? Merge attribute sets using //, I would use a nested attribute for `x` on the left side, this way in the second example where the right attrset overrides `x`, it is clear that the value of the right attrset replaces completely the value on the left. So `{ x.a = 1; } // { x = 2; } => { x = 2; }` concatenate paths and strings IMO is confusing because it doesn't answer the questions what and why is there a difference between a path and a string Named arguments as attribute set; I would rename this to Attribute set as first argument. IMO it makes it a bit more obvious that it's a function with one argument that is an attribute set.	06:04:28
4 May 2024
	@theophane:hufschmitt.net left the room.	15:55:46
	Someone S changed their display name from SomeoneSerge (is taking time off and doesn't want to hear about it) to SomeoneSerge (Way down Hadestown).	21:03:58
8 May 2024
@idabzo:matrix.org	I won't be able to attend the meeting today, but I left two notes in the meeting agenda.	17:48:28
garbas	I also won't be able to attend. I'm too exhausted.	18:35:49
avocadoom	In reply to @garbas:matrix.org I also won't be able to attend. I'm too exhausted. Same goes for me	18:39:05
Albert Chae	I also can't make it today, haven't worked much more on my issues/PRs but will have an update by next sync	18:39:36
djacu	Only Tom and I were able to attend. Since there are some important topics on the agenda, we decided to wait until the next meeting to discuss them with the rest of the team. Other than that, I added an update to the minutes about the cheat sheet. Hope you all get some good rest. Catch ya next time. 👋	19:10:14
9 May 2024
	Someone S changed their display name from SomeoneSerge (Way down Hadestown) to SomeoneSerge (UTC+3).	17:11:48
10 May 2024
djacu	Hey marketing teeeeeeeeeeeeam https://github.com/NixOS/marketing/pull/7	06:11:59
garbas	I'm sending you a virtual hug. This is awesome!	14:10:51
avocadoom	In reply to @djacu:matrix.org Hey marketing teeeeeeeeeeeeam https://github.com/NixOS/marketing/pull/7 Amazing!	14:18:49
11 May 2024
@idabzo:matrix.org	you're the master of LaTeX djacu can I have a discourse post about it to schedule a social media?	11:15:26
djacu	IdaBzo: done! https://discourse.nixos.org/t/official-nix-language-cheat-sheet/45244	15:30:21
	Find me at aleksana:qaq.li joined the room.	18:43:59
12 May 2024
	@man2dev:fedora.im left the room.	11:24:00
13 May 2024
	Arian left the room.	17:44:00
14 May 2024
	infinisil changed their profile picture.	17:45:32
16 May 2024
	@piegames:matrix.org left the room.	19:01:40
@janik0:matrix.org	Hey, I think this affects the marketing team https://chaos.social/@ordnung/112453054938133742 Just wanted to post it here so it doesn't go unnoticed.	22:21:19
djacu	Is this: related to something bigger or are you just making sure we are aware of the rules because we have a social presence there	22:32:55
@janik0:matrix.org	In reply to @djacu:matrix.org Is this: related to something bigger or are you just making sure we are aware of the rules because we have a social presence there Some of the pictures, like for example: https://chaos.social/@nixos_org/112376571947896815 look very ai generated which with the new rules need to be marked as such. So I wanted to share it here so we don't break the rules	23:40:15
djacu	In reply to @janik0:matrix.org Some of the pictures, like for example: https://chaos.social/@nixos_org/112376571947896815 look very ai generated which with the new rules need to be marked as such. So I wanted to share it here so we don't break the rules Gotcha. Thanks for sharing this with the team. I appreciate you looking out for us.	23:42:05

Show newer messages

Back to Room ListRoom Version: 6