It's the sort of thing that makes me really, really sad for the people working there. That crazy breakneck pace cannot be good for mental health.

What if, get this, we put the bash scripts in yaml. And then put it in kubernetes.

Bluegrass and folk ain't bad. Modern country on the other hand...

Shift C

Blame the thousands of supply chain attacks.

He probably bought Overwatch 1, which was turned into F2P overwatch 2.

I think too many people forgot the satire in the original name.

You know what's cool fanservice? Andor using a Bryar Pistol. You know what's not cool fanservice? Seeing the same 10 characters again and again and again. Seeing the same bar in an enormous galaxy.

Kenobi at the very least added some linking character development between ROTS and ANH, despite how awkward some of it was. So that I'm OK with.

Trad bike.

There are "daily" quests that you can reroll into scrip rewards IIRC.

I'd agree more if most docker stuff didn't depend on running as root.

Slay the Spire is a complete 10/10 for deck builder roguelike.

Got a source for the majority claim?

If you select the spell by filtering by spell slot first does that work?

I do wish I could hit a key chord or something to show a terminal of what is happening under the hood with Windows...

It's barely rating the quality of the actual water coming from the taps. That's a single datapoint among 6 other factors, like customer service of the water utility.

And the source of the ranking (JD Power) doesn't really list any breakdowns of that either.

You're thinking too rigidly IMO. Twine/rope and a spool. Pull one way to fully open, pull the other side to open it the other.

Having played DOS2 with a controller & split screen, it worked just fine.

Consider that a 'username+password' is much harder to 'revoke' individually. As in, you can have 3-4 API keys in use, and can revoke any one of them without having to change a password.

You can also change password independently of the keys, or have it linked so keys are revoked on a password change. It also allows traceability as to where accesses are coming from (auditability). If everything is using the same client-id+secret (or usn/pwd), you don't know which 'client' is doing what.

Define production lol. I've used it for a CI cluster for a few years. Have had to recreate it a few times due to database corruption (despite using etcd across 3 nodes).

Honestly Rancher management is more of a pain than manually managing via ansible or something. And swapping to CRI-O backend instead of containerd js a huge pain for Rancher/RKE2, but pretty easy with k3s.