erikw

Reflecting on it, I guess my OS config has turned into a codebase. I have a single Nix closure that includes all my OS config, all the services running on it, and all the small utilities that need to be compiled from source (either because they are something I wrote, or something that isn't packaged in Nixpgs). I'm not sure whether this is considered best practice or not. To your point though, I would be unaware if an upstream maintainer released a security patch for something that I'm compiling from source, because I am pinned to a specific Git commit. On the other hand, I can just point an LLM at my Nix source, and ask it to scan it for security issues periodically. I do this from time to time with one of the smart models, but it might be an interesting experiment to set up a daily scan with an inexpensive or even a local model.

I think people are unfairly downvoting this comment, but I do want to drill into your point (1) a bit. You're right that you can't really do a delta patch in NixOS. But I feel like that is so so so important these days with active supply chain attacks. I don't want a 200kb change to a core library that is "claimed" to be backward compatible to be able to make its way into my codebase. In an ideal world sure, there would be some way to prove that the update doesn't break anything and isn't malicious, and that is certainly possible for some limited subset (provers like Rocq, OS functionality like BSD Pledge, etc), but for now this is mostly based on trust.

I was so disappointed that Valve chose Arch as their base for SteamOS. SteamOS is excellent, and all the work they do has gone back upstream to make Arch and Linux gaming better, but I feel like it was a missed opportunity. I've always thought that NixOS (and immutable distros like Fedora Silberblue etc) are perfect for embedded or consumer appliances. I feel like a bit of help from a company that actually uses NixOS in a mass market product would really push it over the edge in terms of usability.

I think it depends on what they want it for. I can imagine NixOS being perfect for user workstations for example, as an alternative to Windows workstations managed with Active Directory.

I imagine you have a lot more experience than I do packaging for NixOS and other distros given your product, but in the few cases that I've needed to run a binary, I just wrap it with a flake and it's done. I also stay on NixOS stable, so I avoid the sharp parts of "bleeding edge". In my experience as a desktop user, I've never had a failed rollback since using NixOS as my primary OS since around 2016. However, whenever I try to use it as a server OS, I often do hit the pain point you mentioned around statefulness. More specifically, the happy path is extremely happy, but once you need something off the happy path, you find yourself creating some really ugly glue to get it to interface with the happy path. The pattern I've settled on is using Podman quadlets for most services, but that isn't without pain either. Then you find that you've become a Unix sysadmin, managing different UIDs for rootless podman, different network domains, dealing with permissions issues, etc. I'm currently experimenting with microvm.nix to see if that will be cleaner, but no conclusions yet.

Very interesting that Fable took more creative liberties. Have you tried giving Fable the same task, but also specifying that it implement a pixel-perfect design? I think that I prefer the Fable implementation. I find the UI elements in the Fable implementation to have more contrast, which feels more usable to me. I also like how the right padding on the "Book Your Escape" CTA in the upper right matches the top and bottom padding, which I think is an improvement over the mockup.

You can programmatically update DNS whenever your dynamic IP changes. One issue though is that some residential ISPs prohibit webhosting in their terms.

I don't know about this... I think that the "expert" AIs on RTS games just get more resources (not compute resources, but in-game resources) so they can create more units. I'd love to play against an AI component that has the same resource collection speed as the human player.

I'm surprised that you can get non-attendant citizenship in Canada. They don't even give automatic citizenship to children of Canadian parents born outside of Canada (maybe if both parents are Canadian they do, but my experience is with one Canadian and one American). US citizenship for a child born outside of the US to US parents is as simple as bringing their birth certificate to the consulate. And if you marry a Canadian, they won't give you residency unless you physically reside in Canada.

Saint Kitts and Nevis sells passports, so I imagine that is the rationale. I see some other microstates on the list that fit that pattern as well.

Love Plato- it’s so performant! I’ve always wondered why Kobo doesn’t just throw out what they’ve got and fork it.

Have you verified that these "academic bureaucracy roadblocks" exist? Surprisingly, I was able to pick my studies back up after almost 20 years, and not only were all of my existing credits counted, but they also exempted me from new requirements that had been added in the subsequent 20 years.

I don't know that that will happen- not even Windows is as smooth as MacOS. But that's because Microsoft and Linux developers are tackling a more difficult problem- getting an OS to work with effectively infinite hardware permutations. Apple has given themselves an easier problem to solve, with just a handful of hardware SKUs and a few external busses.

That said, Android is pretty stable, because a given Android distro typically only targets a small hardware subset. But I don't think that's the kind of Linux distro that most people contributing to FOSS want to work on.

I'd be curious to understand their rationale for not making a small, reasonably priced phone like the iPhone SE used to be. I probably will be leaving the iPhone ecosystem the next time I have to buy a smartphone (even though I use a Mac, iPad, and Airpods, which all work together really well) because I'm uninterested in using a large phone.

Thinking through my own use case, I just use my phone for messaging, maps, and the occasional app, so I'm not going to need a big screen for consuming content. I also don't want to spend a lot of money on a phone, since I don't need any fancy features. So perhaps that intersection of use cases doesn't make much sense to target?