JFC, some of these responses here about I ‘should’ do this or that. This is precisely why Reddit and most social media is cancer and people filled with 0 social and life skills.

I shouldn’t have to do anything. If you have an issue with my crying child, the onus is on you to find another space for yourself to make yourself comfortable instead of mandating what other people should/should not do.

Does that mean that parents should let their kids run around? Hell no. But this also means that you stop acting like another baby and find a way to adjust just like everyone else incl other parents."

FTFY. The problem with this argument is it’s just as self-centered as the others. If your child starts crying or throwing a fit, go to the bathroom or something, soothe it, and come back. It’s not that hard. If your child isn’t poorly behaved, it won’t cause any other problems. Don’t let your child bother other people by being a nuissance. It’s not on them it’s not their child.

These are only definite articles, not pronouns.

deleted by creator

My new background

I’m aware, but the appimage I run (Slippi Launcher) will run other appimages, and appimage-run can’t handle that, since it extracts the appimage, then runs the contents, but it won’t automatically do that for other appimages that are run.

Which is why I used a Distrobox and it was awesome, worked like a charm. I used Arch previously, and I just made an Arch distrobox and it worked perfectly.

Now I want to try this.

Sorry for the late reply. In the 2 weeks I’ve still kept using it and I learned a lot! But a lot of my musings still stand, at least in my mind, but after thinking a little longer, a lot of the thoughts I had also apply to other distros as well.

To answer what you asked in final, a good hypothetical that might answer it is something like GNOME. If the nixos channel blew up in a doomsday scenario, I’d be stuck maintaining my packages myself, right? And I use the doomsday scenario, because the problems here apply for self-made packages as well, but it’s easier for me and maybe others to wrap their head around the problem I’m getting at. So with GNOME, I’d have to update every single dependency manually in my nix files. With something like Arch/Alpine I could just have those files, and they have these really neat scripts where I can just bump the version, and it’ll download, set the hash up, and bump the version all for me. With Nix there are no such tools. I can’t just automate the process, nor is it feasible to do this type of thing manually. As new features are added, so are new options needed to activate those features. And yes, although in this scenario, I would probably just opt to not add these options and set it up myself, when making a package for the general public this isn’t the case. If GNOME adds a feature (idk why I picked GNOME I haven’t used it in like 5 years) to have extensions managed by the package manager, I’d have to add an option for what extensions are needed and all that. And this is a lot of work, at least as far as I know. The extensions would also have to be packaged.

Gotcha I’ll start playing around with derivations. I also just came to the realization that because of the magic of Nix, I can try these things, and if it breaks it, I can just roll back.

So I can use something like systemd.services to make my own services as well? Because I’ve been wondering how to do this as well.

Gotcha yeah that makes sense, so I’ll start doing this as well.

I didn’t know this before, but a lot of comments said the same! I think I’ll start doing this.

I use Distrobox with my NixOS machine for when I need AppImage support (or some random binary that isn’t equipped for Nix’s weird ass directory layout) and it’s amazing! Pretty much native speed, and when I’m done with it I can just wipe it out. Perfect!

Mm this could be a problem because server load is too unpredictable. I would actually say just randomize the list, so that it kinda does its own “load balancing” by incentivizing to pick whatever random top one it selected?

I could’ve worded the configuration part a bit better. My gripe wasn’t necessarily with that, but more with “If I ever had to make my own package from scratch including dependencies, this would be practically impossible” Nix’s derivations and other packaging information is crazy complex and keeping track of versioning, etc. is a nightmare. I think often about doomsday scenarios for systems. It happens, just look at CentOS and all that, so my main thing was if something like that happened, could I maintain the packages I use manually, and the answer was no. Of course I’m not in a doomsday situation, so I’m fine with it as it is. It’s just a thought I had, and that was my conclusion.

I guess I could’ve worded this better but my second problem was: I would like to do everything declaratively. What do I do when a package doesn’t have its own declarative configuration options? Before it was simple because it was imperative, so I could just change the config file, but not so much in NixOS.

Hmm actually yeah this is a good idea, but the problem is that there’s so many servers that I feel that after choosing criteria there’d still be a bunch of servers in the list and the problem remains, right? Just bouncing ideas. I quite like this idea though.

How?