The argument shouldnt be men vs. women, but people vs. those who exploit us, or people vs. the problem

This is what I tried to hint at.

On the other hand, men on average live shorter, and we just go “well it’s just risky behavior and physical labor I guess 🤷‍♂️” and they’re aren’t any task forces for that either, truth is we as a society don’t care enough about these issues regardless of sex

pacman is very fast and handy. The (in)famous pacman -Syu had you system completely up to date in record time.

Sometimes I miss its speed and simplicity

I mean peertube exists, and it actually integrates into the fediverse…

Then why do they vary by hotel?

This is just silly. I recently saw Las Vegas hotels doing something similar though to a much lesser extent where it’s called “resort fees”. Should be illegal but it doesn’t affect me since I’m not traveling to the US

I was talking about playbooks mostly, not individual tasks.

E.g. if you have a playbook where in one location you make sure a package is installed and in another to add a line to its config files, you need to ensure installation is performed first.

Another generic example is conflicting definitions, e.g. you define a package as present and somewhere else you define that one of its dependencies should be absent. Depending on the order, you either get an error or it works fine (but ignores the package absent directive). Or is my understanding wrong here?

Ansible, the declarative configuration manager

Ansible declarative? That takes a lot of effort I think.

Well, at least for nginx, you can specify the root (or alias if required) directive; to me, it makes very little sense to rely on defaults, you need to specify your servers / virtual hosts anyways, might as well make the configuration more self-documenting…

There’s also https://uapi-group.org/specifications/specs/linux_file_system_hierarchy/ nowadays, which aims to build on the FHS.

Well, /var/www is in fact not part of the FHS, not even optional… it doesn’t exist on my machines either. I think the better choice would be /srv/www which is an example given at https://refspecs.linuxfoundation.org/FHS_3.0/fhs/ch03s17.html

Is /var really such a mystery? I always understood it as the non-volatile system directory that can be written into. Like log files, databases, cache etc. /var/tmp it’s somewhat weird because a non-volatile temporary folder for me is just cache, and /var/lib is named somewhat weird because it doesn’t hold what I’d usually call libraries.

Not pictured: /opt, the raccoon

How would a new format be backwards-compatible? At least JPEG-XL can losslessly compress standard jpg for a bit of space savings, and servers can choose to deliver the decompressed jpg to clients that don’t support JPEG-XL.

Also from Wikipedia:

Computationally efficient encoding and decoding without requiring specialized hardware: JPEG XL is about as fast to encode and decode as old JPEG using libjpeg-turbo

Being a JPEG superset, JXL provides efficient lossless recompression options for images in the traditional/legacy JPEG format that can represent JPEG data in a more space-efficient way (~20% size reduction due to the better entropy coder) and can easily be reversed, e.g. on the fly. Wrapped inside a JPEG XL file/stream, it can be combined with additional elements, e.g. an alpha channel.

I dunno man. I spent way less time configuring my machines on NixOS because it just works. But in fairness, that is after I have spent a lot of time learning it (compared to classic systems that is, not a lot compared to NixOS maintainers who write way better module than I do). Now that there is a foundation, I just run the updates. It’s almost scarily stable. And the ability to group related settings together is such a bliss because you no longer wonder about “what did I do to enable X”, just open the file, it’s all in one place. Stuff that could be three completely different things (e.g. a service specific config file, a PAM entry and the service activation itself in effectively 5 lines. Want to do something for multiple services? Just map over their list. Etc

I happily used Arch for 15 years and after trying NixOS on a decommissioned machine for one day I switched over everything as fast as possible. And I did try out Ansible on Arch, so it’s not like I didn’t try management via a tool. But using a system like NixOS just solves sooo many potential issues.

It obviously comes with downsides, for example there is no quick configuration change. Changing something small requires another evaluation. Still worth it

Did you know that the suffix for nix documentation files is, coincidentally, .nix?