What brand/model of pants can you recommend?
![](https://lemmy.world/pictrs/image/44bf11eb-4336-40eb-9778-e96fc5223124.png)
You're playing Devils Advocate, and you probaly know it xD
Anyway, I prefer NixOS for it's declarativity, reproducibility and immutability.
Example: You want nginx with acme setup? Just tell it to, and NixOS will figure out the steps to reach the desired state.
What would you tell a direct ancestor of yourself, living in the year 2024?
EDIT1: fix "DE" -> "DM"
Nix has an open issue on integrating IPFS support.
There's also an old tutorial.
Forgetting time, space and everything else while I write code.
Not that I've almost set the kitchen on fire before by forgetting the pizza in the oven while writing "this one little function".
I use a reproducible, declarative and reliable system btw.
I also use flakes btw.
Fork the parent and orphan the child, isolate it's environment and kill it as well, once everything conpleted.
You sound like the devil trying to trick me out of my souls posession.
Total amount of Energy consumed
Trivium - Vengeance Falls
Nushell
I've recently switched over to NixOS in gradual rollouts to my systems:
Stage 0 (~2h):
Stage 1 (~3d):
Stage 2 (~4d):
Stage 3 (~7d):
Stage 4 (~21d):
Stage 4.5:
Stage 5 (~6d):
Stage 6 (tbd):
Edit 1 (added personal experience): I'm a computer science student and have been using *nix as a daily driver for half a decade, my previous daily driver was arch for about two years. I spend ~1000h/y coding on non-University or Work related projects. I'm at a point where I can typically pick up a the basics of a new language in two to three weeks and write simple programs with it -> library/specific knowledge comes with usage.
After that, add Omniscience
Dependency Hell, begone
Easy and fearless updates
My system configuration can be found on git.sr.ht/~sntx/flake. I've linked the file tree pinned to the version 0.1.1 of my config, since I'm currrently restructuring the entire config[^1] as the current tree is non-optimal[^2].
The documentation in the README in combination with the files should cover most of what I've described, with the following exception: disko is not present to the repo yet, since I've set it up with a forked version of my config and the merge depends on finishing the restructuring of my system configuration.
[^1]: The goal is to provide definitions for desktops, user-packages, system-packages, themes and users. Each system can then enable a set of users, which in turn have their own desktop, user-packages and theme. A system can also enable system-packages for itself, independent of users. If a user is enabled that has a desktop set, the system will need to have display-manager set as well, which should launch the users configured desktop.
[^2]: The current config assumes a primary user, and can only configure a single DE and apply the application/service configs only to that user.
Note to self: Write a fictional story featuring me at some point.
inifinity + 1 = infinity
Try ℵ₁ wishes!
A massage - back, shoulders and neck
Nice! I love trying out new tools. This one seems straightfoward to use.
There are also these two blog posts by elis on setting up tmpfs specifically. Though these posts rather are setup guides, than "talking about the philosophy" of systems design.
Two people meet, one doesn't come
Single command to compile & install packages from many git repos
Does it support the ability to act like the sort
command, though switching to a different term "buffer", sorting visually with a defined (i.e. through config file) speed, and then returning the sorted entries to stdout?
Please tell ^^
+ Impermanence
That's a nice album!
Can turn basically any distro into nixos in minutes
That's the setup!
Though I prefer the mix of flac/opus.
There are scripts for yt-dlp out there that allow you to automatically download an entire artists discography (yt), which I recommend if it's legal in your country.
Reproducible
^ This
Nix(OS)'s biggest killer feature for me is that I never had to update, wait for updates or fix updates after setting up the modules properly and getting CI set up for my git repo -> all systems are build before the update is rolled out, if the build fails, the update won't be rolled out. Systems decide for themselves when to update and how they should handle them (i.e. server vs. desktop).
That goes for all my systems: Laptop, PC, Servers and VMs
Behaviour adoption?
I'd fall off my displaced chair and have my left kneecap stuck in the drawers. I guess I'd die if that merge of my knee with the drawer would result in fusion.
I think Jumuta is referring to LibreWolf, a fork of Firefox with some hardening pre-applied. I use it on machines on which I don't want to spend time configuring my browser.
Everything will be LISP in the future
I'm suprised nobody mentioned nebula: A scalable overlay networking tool with a focus on performance, simplicity and security.
I've been running it for about two years on multiple machines and it worked flawlessly so far. Even connecting two hosts, both behind mullvad-vpn tunnels.
The only downside is, that you have to host your own discovery server (callled "lighthouses"). One is fine, but running at least two removes the single point of failure from the network.
Unfortunately time does not care about people