lemmyng

Better than the inpatient toilets with the sensor that flushes the moment you lift your butt. I did not ask for Poseidon’s wind Willy!

Looking forward to the sandwich tetrahedron.

I will never forgive JSON for not allowing commas after the last element in a list.

Yeah, you’d have a LoadBalancer service for Traefik which gets assigned a VIP outside the cluster.

virtual IP addresses

Yeah, metallb.

The container is reproducible. Container configuration is in version control. That leaves you with the volumes mounted into the container, which you back up like any other disk.

It’s not that Seagate improved (which it may have), it’s more that WD has noticeably declined. It’s not a race to the bottom (yet), but there’s effectively no competition any more, so they aren’t incentivised to improve quality.

I think there’s a mistake, I can’t fit “neovim” into 8 across.

Figure out the uid/gid (numeric) for the user in lxc, then change the data permissions to those.

UNIX time uses a Julian calendar date as a reference, but is independent after that.

As for the 13 month calendar, it’s about as nice as cloverleaf interchanges: appealing because it’s symmetrical, terrible in practice. Having the days of the month always align to the same weekday means leap years would make things even worse because every 4 years the entire calendar shifts. And if you skip the leap day as a holiday then you just make calculating dates from an epoch like UNIX time even more convoluted.

So much to ponder…

Everyone talking about the toilet, but what about the oven windowsill?

Fuck, you gave me half a heart attack thinking I overslept Sunday.

Regulation won’t work, because regulation moves slowly, and these companies find workarounds fast. And as long as the cost of breaking the rule is less than the benefits of doing so, it’ll be “just the cost of doing business.”

Use -m and limit the build job’s memory so it doesn’t kill the docker daemon.

I’m out of the loop. How does Carmen Sandiego fit into the whole init system debacle?

To be fair though, the chance that every Lemmy instance goes down at the same time is so much lower than Reddit going down. Sure, my instance might be unavailable, but I’d be able to hop onto the next one and continue.

Brian Kernighan. Got the chance to have lunch with him!

I’ve seen it successfully happen due to licensing costs and cloud migration (MSSQL->Spanner), as well as for scalability reasons (vanilla postgres->cockroach). The first one was a significant change in features, the latter did sacrifice some native plugins. In the first case the company was using vendor specific features, and rewrote the backend to fit the new vendor.

There’s vendor agnosticism, and then there’s platform agnosticism. Writing your code so that it’s not tied to one specific implementation of postgres is fine, and lets you use a compatible drop-in. Writing your code so you can swap MSSQL for Oracle or Aurora or whatever at will does not make sense. In every case of attempted platform agnosticism I’ve seen they ended up abandoning the project within a year or two with nothing to show for it.

What this actually shows is how much previous governments fucked up and how desperate and angry the Argentine people were that this clown started to look like a good idea. To those with an outside perspective it was always obvious that this would only end badly, but to them it was an “any port in a storm” situation.