text stringlengths 0 2.02k |
|---|
**Jerod Santo:** Lots of emojis. |
**Gerhard Lazu:** They convey so much emotion. |
**Adam Stacoviak:** \[52:01\] In regards to the community though, we can say that we have a dev channel in our community Slack... And if I'm keying off of what Jerod's saying, it's like "Where can people hang out at?" So we already know that Changelog.com/community is there, it's free to join and it's open... We alread... |
I think we've already paid for the price of admission, which is free, and the infra is there, thanks to a free Slack, and the community, all that good stuff - it's done. So a matter of moving some of that conversation from Dev to Ship It, or just promoting Dev to what could be Ship It? |
**Jerod Santo:** Either way, in terms of the logistics of that getting done, it sounds good to me... But I think we should definitely have a Ship It channel where folks can hang out and talk, and throw ideas out there, and have a place to discuss the show and things around the show; it doesn't have to be about the show... |
**Gerhard Lazu:** Do we have comments enabled on episodes? |
**Jerod Santo:** We do. |
**Adam Stacoviak:** Yeah... |
**Gerhard Lazu:** Okay. So that's one. |
**Adam Stacoviak:** ...for now. |
**Jerod Santo:** \[laughs\] |
**Adam Stacoviak:** If you listened to a recent Backstage, for now. \[laughter\] |
**Jerod Santo:** We thought about turning them off, so you can go listen to tht conversation... And we actually agreed on turning them off, and then I just didn't do it. \[laughs\] |
**Gerhard Lazu:** Okay... |
**Adam Stacoviak:** Yeah. |
**Jerod Santo:** So we might leave them on forever because of laziness. Or maybe they'll disappear. But I don't know. Go listen to that Backstage episode; what was that, 16? All the emotions around comments. But for now they're there, and I don't know; I'll just leave them on, because people do seem to like them. |
**Adam Stacoviak:** And since then - this is a micro-version of that conversation; I've seen more adoption of our comments... And especially that recent blog post you've got there, Jerod... |
**Jerod Santo:** I wonder if that episode spurred on-- |
**Adam Stacoviak:** If it weren't for that, you wouldn't have people talking to you. |
**Jerod Santo:** Yeah, I wonder if that episode's spurred on more comments. They're like "Wait a second, these guys have a comment section? I didn't know that till they posted a show about it." |
**Adam Stacoviak:** And then even since, I've look at our design of it, and I think that for a signed out user it could be -- we could do better design to make a better effort to encourage discussion... |
**Jerod Santo:** Oh, yeah... Like, actually an emoji picker? |
**Adam Stacoviak:** So there's definitely some things we could do... |
**Jerod Santo:** Reactions... There's all sorts of stuff we could do. |
**Adam Stacoviak:** Just guides to higher value content, really. Higher value comments. But that recent post you did - you might as well timestamp it. That got a lot of comments itself; the Backstage episode we're talking about is episode 16, accurately titled "Let us know in the comments." So yes, let us know in the c... |
**Jerod Santo:** So yes, there are comments on each episode, so it's a great place to have conversation... Especially, I like the permanence of those, in terms of it's attached to the episode, so if you have follow-up links or questions regarding the content, it's a great place for that... Whereas, of course, there's a... |
**Adam Stacoviak:** They do. |
**Jerod Santo:** And elsewhere... |
**Adam Stacoviak:** They have lots of conversations on LinkedIn. |
**Jerod Santo:** And in our Slack... But there's some value to the comments on-site, so... |
**Adam Stacoviak:** Yeah. It's worth it, in my opinion. But if you're listening to this and you're thinking "Well, one, they've answered my questions around community...", because clearly we just-in-time produce the future of things, so we just determined that we're gonna have a community, and it'll potentially be the ... |
If you wanna join the community, it's there, Changelog.com/community. No debate about that. And if you care about shipping it, then you should ship it with us. |
**Gerhard Lazu:** Also, if you care about all the other things that happen before shipping it, and after shipping it... |
**Jerod Santo:** And while you're shipping it? |
**Gerhard Lazu:** And while you're shipping it, yes... \[laughter\] That's almost like a point in time, but there's so many things happening before and after. And it's not like a single event. You find yourself shipping it, and you would like to think that every time it's the same; that's what we aim for, it's an ideal... |
**Adam Stacoviak:** Yeah. |
**Gerhard Lazu:** I think it's those things which are really interesting - how do you build systems where shipping is so easy and straightforward that you don't even think about it? I think we were rather fortunate that that was the case for us... Just git push and everything will take care of itself. Or merge, if ther... |
**Adam Stacoviak:** Well, you hear it here first. Gerhard, our resident SRE for hire has been promoted to podcast host, coming at you weekly. Changelog.com/shipit. I'm excited, Gerhard. I've been a big fan of what you've been doing with us for so long, and I'm glad to get to a weekly cadence, where it makes a \[unintel... |
• What Nix is: an ecosystem of tools for developing, building, and deploying software, combining language, package manager, and unique concepts |
• Origins: research project started by Eelco Dolstra in 2001, sponsored by grants, to apply functional programming to solve packaging problems |
• Domen's introduction to Nix: 2012, introduced by a friend, Florian Friesdorf, to solve problems with package dependencies and breakages |
• Key features: rollbacks, binary cache, source distribution model, and atomic operations |
• Relationship to other package managers: Nix is a replacement or augmentation, offering a different approach to package management |
• Nix ecosystem: Nix language, Nix package manager, NixOS, and other components, offering flexibility and portability across Linux distributions and macOS |
• NixOS: a Linux distribution, but also a package manager, and can be used as a whole separate thing or to build and deliver software |
• Nix package manager supports Linux and macOS operating systems |
• NixOS is a Linux distribution built on top of the package manager, suitable for desktop and server use |
• Nix has a large ecosystem, including tools for DevOps, home file management, and package deployment |
• Nix has a package management system, where most packages are precompiled binaries that can be patched or customized |
• Nix Packages are a collection of packages available for installation, built from source and including binaries |
• Reproducible builds are a core tenet of Nix, ensuring that packages have not been altered or changed after installation |
• Features such as rollbacks, atomic upgrades, and reproducible builds make Nix a unique and attractive package manager |
• Nix allows for isolated environments, remote building and deployment, and seamless package management across systems |
• Nix Packages use a top-level file called all-packages that imports other files, such as firefox.nix, which describes how to build Firefox |
• The Nix language uses a derivation function to build packages, which takes inputs (key-value pairs) and passes them to a builder (an executable) |
• The builder runs in a sandbox environment, isolated from the file system, to ensure reproducibility and make the build dependent only on the inputs |
• Nix calculates a hash of the inputs to uniquely identify the package and its source |
• Packages are stored in the /nix/store/ directory and linked together in a file system hierarchy (profile) |
• Profiles can be stacked and managed, with each user having their own profile and the system having a system profile |
• Garbage collection involves deleting packages that are not in the profiles, and can be done globally or for a specific profile |
• Profiles are symlinks that point to the file system hierarchy, and can be managed and garbage-collected separately |
• Nix store is mounted as read-only, providing a guarantee that packages cannot be modified once installed |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.