Huh? I’m confused, where exactly was I hateful?
Disappointed, perhaps? Especially considering that the only two accidents I’ve been in during my entire life have been idiots with “ice and snow” (non-studded) tyres ice-skating into the back of my car.
Sorry, but American statistics aren’t fully relevant to their comment. Sweden has much more rigorous laws and controls regarding tires, and a particular difference is also rules regarding the stud length and depth.
Yes, our studded tires still damage the roads a bit more than “normal” tires, but it’s not an astronomical difference. The lifesaving and healthcare costs associated with studded tires weighs significantly higher. Your life is considered much more expendable in the US as well, so of course they say you shouldn’t use studded tires on ice… whereas our government research institute says you absolutely should.
I also assume the US uses really cheap asfalt or something? Or because of higher speed limits? Worse driving styles: intensive speed changes instead of calm tempo driving? Despite like 65% of cars using studded tires here, I’ve seen less road work here in my entire life than during a single year in the US. Dunno.
Do with squash just in case
It’s cooler to use 172.16.0.0/12 because everyone just sees “192” and thinks it’s part of 192.168.0.0/16.
Congratulations, you got hired somewhere great! Or your team is filled with masochists, who knows.
Have you livepatched the kernel though?
But why should we think so much about the final result when it’s out of our hands? Without you, these people probably wouldn’t have gotten any care whatsoever (or at the least, delayed with it -> higher risk for worse results).
Unless you did stuff to worsen their condition, you’ve undoubtedly saved many lives, and many people are very thankful for your contributions. So, thank you!
It might work in WSLg otherwise?
Why not RHEL then? It even has “enterprise” in the name!
Does IPv6 scare you so much that you start craving the monstrosity known as NAT44?
That’d be an unusual setup. If you have users deploying containers on your host – that you trust enough to run whatever containers, but don’t want to give them ssh to the host – you’d usually have some kind of frontend such as Portioner, where you can have container exec and such.
Containerization is not virtualization. It’s very possible to break out of containers, especially if configured badly, or if there are any found exploits in the container engine or even the kernel. Containers are “good enough” for the majority of projects, but it has never been designed to be a truly hardened sandbox.
Basically, if you’re running an OpenSSH server inside a container, it’s likely that you’ve gotten the wrong ideas about securing your environment, and thus some old libraries in an old Debian image is the least of your worries.
Who’s running OpenSSH servers in their old Debian containers anyways?
Wow, only 100 calories!
Security-wise, yeah? IIRC Microsoft is very nonchalant with checking that there’s nothing malicious in the plugins on their marketplace.
It’s not red, so it’s not a dangerous button.
Aha, okay, much clearer what you meant now. Yeah, they surely get a kickback for each new subscription.
Why are you buying a phone plan if you’re not using the mobile network?
You understand that SIM cards aren’t actually active until they’re connected to the network for the first time, right?
“wow, we’ve made our postgres so good and fast… by moving heavy workloads to a NoSQL database engine”. Truly mind-blowing, OpenAI. Just like their LLM service, not even their technical staff can stop themselves from lying and writing misleading statements.
The only interesting part could have been what they use for caching… but of course they don’t give any details at all. And all the rest is already well-known DBOps stuff… and basically all automatic with stuff like cnpg.