Ambroisie

I'll be honest, that does not sound "easy".

It is straightforward, but so is the NixOS module system, and I could describe writing a custom module the same way you described custom Docker images.

I haven't double checked, but my recollection of that story was that they were using Git as part of the operations at runtime, not (just) as a development dependency.

Do you have a link to a more in-depth analysis of the queuing theory for these numbers?

I don't think you can equate CI/CD unit tests and killing humans with 2 tons of metal.

I have to say, I don't see what makes it handle the criticism from the OP. It looks exactly the same as every other Dyson product I've ever seen.

I'm still in love with Caml from my time in prépa, one of the reasons I'm sometimes eyeing JS for a move.

I think OOP meant to say that the `.envrc` file _is_ committed, but they want to do local changes _without_ the possibility of them getting accidentally committed by mistake.

My thinking is that the dev _did_ work on it for X amount of time, but as part of their contract is not allowed to share the _actual_ history of the repo, thus the massive code dumped in their "Nobody expects the Red Team" commit?

Opening it in a new tab on FF on Android works fine on the first try.

This looks like a worse version of the one I used, the TI nspire CX CAS, for about the same price.

I run my own self-hosted synapse (backend) and element (front-end).

It's been working flawlessly since I deployed it (about 2 years ago now).

Can you explain what you mean, about unsafe friendliness in the standard library?