Somehow Source 2 has better lip sync than many modern game engines I've seen.

Who in the blue F thought The Wire "started slow"? Is that shorthand for "it didn't wrap everything up by the end of the first episode?

Everything you typed is true in the Scandinavian countries, and they have low birthrates too. Not as low as Japan, but still well below replacement rate.

VMware will still be around in 5-10 years, easy.
The companies they're dealing with will pay whatever price, because by the time "we should have switched years ago" becomes cost effective, the current CEO of that company will be out the door. And their successor will be dealing with a sunk cost fallacy. Lather, rinse, repeat.

See also: Oracle customers (also know as "hostages").

FFS, Symantec still has antivirus customers and they've been through two PC refresh cycles since the Broadcom takeover. How hard is it to deploy a different XDR to a laptop when it's being built? Yet they don't bother.

WSUS still very much works in Server 2025. It's now marked as "deprecated" which means they're no longer changing/updating it (not that they've really done that since 2012R2 anyway) and also "don't be surprised if it's not in the _next_ server release.

Even if they don't keep publishing catalog updates until the 2034 EOL of Server 2025, I would be shocked if they cut them off before the 2031 EOL of Server 2022 (given that under Server 2022 it's still very much supported).

Sure, but to be fair, I don't think there's been an innovation in WSUS since at least Server 2012. You still need the same Powershell scripts to prevent it from falling over now as you did then. The entire workflow has been almost pointless for years - Microsoft releases what, two cumulative updates a month and maybe an out of sequence security update? We're not approving/rejecting twenty updates individually anymore. The "oh shit the new update breaks something" problem can be solved with rings and deferrals now. Plus you're going to maintain a VPN so your remote users can get updates?

"Deprecated" means "it's going to die eventually". It's still in Server 2025 preview, which means it'll be there when Server 2025 goes RC. Which means that people will have _at least_ until 2035 (when Server 2025 goes EOL) to come up with a solution.
At some companies that's _two_ hardware refresh cycles from now.
AND that assumes that they're going to eliminate it from the NEXT on-prem server release, which isn't a guarantee. For example, they deprecated TLS 1.0 and 1.1 in Server 2022, but it's still in Server 2025 (but disabled by default).

And NASA will tell them to go pound sand. This was under a fixed-cost contract, Boeing is responsible for any cost overruns. And if anything, by not delivering a vehicle that can safely take astronauts into space and back, means they're in violation of it.

What is more likely is Boeing will pay the contract termination fees rather than throwing more hundreds of millions at Starliner.

Making the boiler in a steam engine not explode takes a little knowledge, yes.

Redox OS is another microkernel-based toy OS attempt, it's not attempting to replace the monolithic Linux kernel.

This is two fold. At my _current_ company, that's absolutely the outlook. I put out an announcement that (say) Teams is having a problem, everyone grumbles, I'll hear a couple "fuckin' Microsoft"s, but people thank me for telling them. I keep a close eye on things and let everyone know the minute service is restored.

At a previous job, I fought tooth and nail about going from on-prem to O365 (and it was much earlier in 365's history) because that culture was the OPPOSITE of that - if there was a cloud service problem they would have completely expected me or my team to "call Microsoft" and get the problem fixed. (You know, because of all the leverage we would have had with them. /s) We figured if it was going to be our ass in a sling we might as well run the services ourselves. That way, we could make them as bulletproof and redundant as we could afford, and at least if something broke and we got yelled at, it was something we could solve.

Problem is, there are loads of companies out there that can't just "not trust NIST".

And it was the NSA that ruined Dual EC DRBG, NIST only made it one of four recommended PRNGs, they didn't mandate anyone use it specifically (and no one other than RSA, after being paid off by the NSA, did.)

Every time the NSA tries "we're going to develop a standard that has a backdoor we can use" (Clipper, Dual EC DRBG), they get sniffed out and their attempt fails.

OK, good, I'm not the only one who hates SELinux. Cool.

Oh, I wasn't white knighting cable companies. I'm not a fan of them either. I was just pointing out that telcos could have gone fiber years back but chose not to (although, given my dealings with telco techs, I wonder how much of that was union pressure to not make the oldsters "learn something new".)

You'll forgive me if I don't shed tears for a company that would sign up third party ISPs to sell their DSL, lock them into a contract, then undercut them by selling to the same customer base for cheaper (or for the same amount of money, but with more advertising spend.)

ILECs teed off on consumers for years, raking in the profits, and not investing it back. Fuck 'em. Just like all the power companies whining how EVs are going to overwhelm the grid and meanwhile you can't find three consecutive power poles that are newer than the 1980s.