noplacelikehome

The Azure docs are abysmal, and obvious quality issues (like copying the entire Windows VM directory over the top of the Linux VM one and forgetting to change things like RDP connection details out for SSH) sit unanswered for months.

I will never understand Microsoft.

I've just ended my Pro plan; enough is enough. I've been debating moving my repositories to a self-hosted forge for a while; it'll be an interesting opportunity to move more CI operations out of Actions and into Nix.

I’ve started to adopt Nix devShells to help keep a record of each project’s dependencies.

If Nix is too heavy, the learning curve for tools like asdf-vm and mise is much lower and offers similar benefits.

I really wish there was a good equivalent for Windows.

It is wholly owned by and accountable to the UK Government, so this is at best a partial truth.

This reads as though your objection is to the scope of systemd rather than its implementation detail, which isn’t where my objection lies.

I have nothing against the service management stack also addressing common principles like logging and on-demand starts a la inetd, but the notion that applications should link against a component of the service manager which is also used by the service manager boggles my tiny mind.

libsystem is such a bizarre abstraction covering far too much surface area. The name alone is a code smell. Why is the same library used for both internal service management and for services implementing on-demand launches and notifications?

Totally valid, but FWIW this can be turned off without becoming a supporter: take a look at the source for the settings page for a hint.