If you replaced them with equal or better talent why not just fire them in the first place? Why ask them to come back to the office at all?

*flat voice*

Stop. Don't. Come back.

That would assume the body has a 100% logical pain feedback loop. It doesn't.

Our "intelligently designed" bodies give us crippling pain for a toothache (a relatively easy malady to cure) yet can let cancer run rampant and symptom free until it's too late to treat.

Which is hilarious because last time I checked Azure runs more Linux workloads than Windows ones. If this spooked anyone it was in 2004 but by a year or two later everyone realized there was no "there" there and just moved on.

How long have they been doing "any minute now" with Proof of Stake? They've been certainly using its "coming soon" status as a dodge for all of 2020 and 2021 to counteract the narrative that all crypto really does is waste energy.

If they couldn't tie it into an actual hard fork of the coin, how serious about switching are they?

Yes. Well, not so much cheating, but the testing environment isn't the same. Instead of a four hour test in an unfamiliar location at 8 AM you can take a two hour test in the comfort of your own home in the afternoon if that works better for you.

https://blog.blueprintprep.com...

Whatever makes you think HIPAA has the remotest relevance in whichever jurisdiction I'm in?

Psst: I don't actually give a shit.

Whatever makes you think HIPAA would be the only law even in jurisdictions in which it does apply?

Because there IS no other law in HIPAA jurisdictions that would apply in this situation?

99% of the people on the internet who speak/write English and claim that they're legally protected from being asked about vaccination status are A) Americans who think B) HIPAA applies in that situation and therefore C) are wrong. So congrats on being part of the 1%.

"Tell me you don't know how HIPAA works without saying the words "I don't know how HIPAA works"".

The EEOC has repeatedly said asking prospective or current employees about vaccination status is permissible.

It's exactly this kind of FOMO shit that causes Americans, as a group, to not take all the vacation time they're owed, or to bust their ass for more than 40 hours a week, every week, at a salaried position, with the promise of a raise or promotion that mysteriously never comes because of "cutbacks".

If 37 of you went to a bar, do you think anything useful is getting done? No? So why would it be different over Zoom? You're going to hear the leader, or a few leaders, bloviate because they like to hear themselves talk, and that's an hour of your life you're not getting back.

So your business was literally unprofitable until systemd existed but you somehow didn't re-architect your processes (hint: if boot time affects production, you're doing it wrong) before that point? You just sat there and bled money?

Worse. Rule of thumb is 5 microseconds per km through fiber (in reality it's a bit faster but it'll never be slower). So in your example that's 35 ms each way, or 70 ms round trip before you add in switching and routing latency.

that causes Lennart Poettering to lose his meal ticket and he has to go back to competing on (non) merit instead of having a 600 lbs gorilla shoving his crap into every major Linux distribution.

He founded Nissan Computers in 1991. Got the domain name Nissan.com in 1994. Nissan Motors had announced the Datsun/Nissan switch in 1981 and was done with it by 1984/1985. Again, he didn't have the nerve to be surprised, he knew exactly what he was doing.

Again... if he hadn't deliberately registered a domain name that would cause confusion with a much larger company HE ALREADY KNEW EXISTED, we wouldn't have heard of this guy. NONE of his companies were just called "Nissan". The company name in question was Nissan Computers. So why did the domain name absolutely-no-compromise have to be "nissan.com"? Because he thought he could get some monetary consideration from it like the rest of the domain squatting dirtbags that were all over the place in the late 90s and early 2000s, and it blew up in his face.

Except he didn't. Nissan.com goes to Nissan Computer's web site - which is plastered with information about the lawsuit that you have to get past to get to his computer services. NissanUSA.com goes to Nissan Motor's US web site.

And I'd have a LITTLE more sympathy for the guy if he hadn't registered the domain name nissan.com knowing Goddamn well a major car company was using it for the past five years. Why couldn't he just be nissancomputer.com? Every other Nissan related name on the net - and there are lots - has something else as part of the domain name, and Nissan Motors didn't go after them. Nissan Motors even registered that domain and offered it to him for free and said in print there wouldn't be a lawsuit if he had differentiation in his domain name. Clearly he was counting on the domain confusion for ad click throughs.