A modern Ethernet PHY already has to support multiple different encoding schemes, MLT-3 for 100BASE-TX and PAM-5 for 1000BASE-T (and PAM-64, etc for higher speeds like 2.5 or 10 gig.) Eliminating the Manchester encoding for 10BASE-T is a logical way to save on cost and complexity, especially since most companies probably don't have a lot of legacy 10 mbit only gear to test with.

For a while the scheme DID matter. From 1.0 to 2.6, evens (and zero) were stable, odds were development.

2.6 stretched from 2003 to 2011 when Linus just declared that instead of the next version of "stable" being 2.6.40 it was going to be 3.0.

Is it ALL TV? Or if it's an emotionally engaging movie, is that more like reading, and only the brain rot TV is "passive"?
What about sitting and listening to music? Is that active or passive?

Yup. Native born women have had a total fertility rate of below 2.1 (replacement) since the 70s. It's been the first generation immigrant women keeping the average up, and even that average has been slipping of late.

As someone who came up on X terminals, the concept of an X system that can't do the standard client/server scheme just blows my mind.

And I remember when X.org was the upstart fork of XFree86!

But at least the "random code" from Stack Overflow was _working_ code. The AI stuff is a crapshoot.

A beginner using AI to "vibe code" isn't going to understand when it's making things up out of whole cloth (like how it has a tendency to hallucinate Powershell cmdlets) and is going to spend more time whack-a-moling the result to get a kinda-working program than they would if they just started with a basic foundation and got better as they go.

You learn to build a skyscraper by first learning to build a house, not by ChatGPTing a skyscraper and then figuring out what you need to shore up to prevent it from falling down.

But if T-Mobile had been able to get that spectrum back, they might not have been able to buy US Cellular, which got them spectrum _and_ customers. They're now solidly in the middle of the pack when it comes to customers (as opposed to before, where AT&T was nipping at their heels) and have _more market share_ than Verizon even though the latter has ~13M more subs (because T-Mobile's mixture of customers is pulling in more money per customer than the other two carriers.)

Not if all the single family housing stock is being bought up by corporations to rent them out, since the surviving children will always take top dollar in cash (with no inspection) from a corporation rather than a mortgage from an actual family.

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?