 | NixOS Marketing | 271 Members |
| NixOS website + marketing team: https://nixos.org/community/teams/marketing.html | 58 Servers |
| NixOS Marketing | 271 Members |
| NixOS website + marketing team: https://nixos.org/community/teams/marketing.html | 58 Servers |
| Sender | Message | Time |
|---|---|---|
| 13 Aug 2021 | ||
 evils | In reply to @jonringer:matrix.orgwhoever shows up to the local hackerspace's birthday https://hackerspace.gent/landing/newline.php | 00:36:24 |
 jonringer | Generally the most notable talks are "here's how this tool solves a bunch a point points, and here's how it does it" | 00:36:46 |
| evils | unfortunately, i switched to nixos early enough in my linux journey that i don't know any of the pain points of other stuff :P | 00:37:34 |
| jonringer | For developers, I would at least include version controlled developer environments, which can be re-used to create containers or a NixOS module (system service). | 00:38:22 |
| evils | yea, nix-shell would definitely need to be covered but i feel like there should be some preamble to that | 00:38:54 |
| evils | i'm also not sure if i should separate nix and NixOS | 00:39:13 |
| jonringer |
Instead of, run this docker container to perform the build, or install these 10 dependencies, you could also just do
| 00:39:21 |
| jonringer | In general: nix/nixpkgs is user land, NixOS is system | 00:39:47 |
 tomberek | Yes, please make it clear that NixOS is "hey, this Nix thing worked, let's do this for my whole system", but is not really the core idea. I've also found the analogy to automatic memory management (from Eelco's thesis) to be a good one for some people. | 00:40:56 |
| evils | In reply to @tomberek:matrix.orgi've been hearing the inverse argument xD | 00:41:21 |
| jonringer | NixOS is... odd. Essentially it's just nix, with enough impurity to apply the changes to the system :/ | 00:41:36 |
| evils | (i am a NixOS user and maintainer) | 00:42:13 |
| jonringer | Idk, nix/nixos can be applied to so many things, it's really hard to give a "high-level overview" of what it does | 00:43:37 |
| evils | In reply to @jonringer:matrix.org* whoever shows up to the local hackerspace's birthday newline.gent | 00:43:51 |
| evils | "water is a very simple polar solvent used throughout the world to create and sustain life" "yea, but why would i want to use it?" | 00:44:52 |
| evils | In reply to @jonringer:matrix.orgexplaining what it actually does i suspect devolves very quickly to technobabble... | 00:46:03 |
| tomberek | how about: "As projects and systems get more complicated, most build systems become fragile and difficult to maintain by humans. A Nix-based build continues to be maintainable far beyond what other systems can handle." | 00:47:09 |
| jonringer | well, the only novel concept that nix has, is that it's able to serve you a store path (or many store paths) with the contents that you desired; insulated from the host system | 00:47:23 |
| tomberek | I want to have a clearer set of "killer features" that we can offer. Concepts like nix-bundle and advanced distribution perhaps. | 00:47:43 |
| jonringer | Everything else is a composition of packages (or nix store objects, if you want to use the "nix" term) | 00:48:20 |
| evils | In reply to @jonringer:matrix.orgi feel like nixers get that that's a fundamental difference that enables many killer features but that statement doesn't "enlighten" anyone on its own (i suspect) | 00:51:00 |
| tomberek | That GNURadio project I had was a good venue for me to describe in my audience's vocabulary the wonderful outcomes of using Nix/NixOS/Hydra. Try to capture what would "wow" them, and emphasize that. | 00:51:26 |
| jonringer | Yea, but it explains how you could build a single package, or a whole OS, or a installation cd, or a VM image | 00:52:00 |
| tomberek | Hackerspace? You can set up a system in the hackerspace to do builds, deploy to hardware sitting in their lab, and they can watch the results via remote webcam..... "you can stay home and still have confidence it works on the hardware you can't bring home with you." | 00:53:44 |
| evils | In reply to @jonringer:matrix.orgwith the same tools, as custom as you want them | 00:54:09 |
| tomberek | or "complicated toolchain for <insert-embedded-thing-here>? no prob, 'nix-shell' is all you need!" | 00:54:25 |
| tomberek | * or "complicated cross-compiling toolchain for <insert-embedded-thing-here>? no prob, 'nix-shell' is all you need!" | 00:54:45 |
| evils | In reply to @tomberek:matrix.orgi think the counter-argument i've heard for that is "just use docker" and it's hard to argue against a tool that works and many people already know | 00:56:25 |
| tomberek | or (a bit more salesman-like): "tired of being able to get something to work, but no one can reproduce your results? Or they can't reproduce your bug reports? Do I have a proposal for you!" | 00:56:37 |
| tomberek | well, for hardware people are a bit easier because they usually don't want Docker between them and their hardware. "it's native!" | 00:57:26 |