The problem with the vast amount of hardware turf that Microsoft covers is different from say, Apples, because Apple highly controls their hardware platforms, and Microsoft by its nature, cannot.

Add in driver components, software legacies, and Microsoft users continue to pay this tax, generation after generation. So indeed these issues ARE similar.

When Oracle updates key functionality, they risk a domino effect, just as Microsoft does. The QA feedback loop can help, but all old code must become crusty because of physics. Reinventing the core code then causes its own ripple effects.

There are ways to fight this, at the risk of business partners going away-- the hardware makers and software vendors with huge installed bases.

Every time a change is made, it would be wonderful to do regression testing. That's why there are "insider" programs, the little beta site for these changes because regression testing today is impossible because the installation platforms are too diffuse.

There is truth in the aphorism, "The bigger they are, the harder they fall.".

Have you ever noticed why no one celebrates Patch Tuesday in the pub? It's because they're waiting by consoles waiting for stuff to break.

Windows, client and server, are a house of cards. This goes far back in history. The citations you challenge are each provably wrong. Ever wonder why the cloud isn't rife with Windows servers? There's a reason for that. Cloud Native Windows is almost an oxymoron. Linux and to a lesser extent, BSD, have taken over that space.

In so many ways, Windows is now a legacy data OS in data centers and for good reason. It's developer community has all but collapsed. It's backwards compatibility with other house-of-cards platforms like dot-net have put ball-and-chains around its neck.

The additions of tawdry pre-release-in-production AI with Co-Pilot causes new train wrecks each and every day.

No serious services developer uses Windows as a new development platform. The metaphors you diss are a dodge. You know exactly what the remarks are about. Windows continues to be a sieve for security. Linux and BSD are far more difficult to breach, correctly configured-- and it doesn't take much.

As a developer, if you are one, Microsoft is putting you to the pasture. Have fun eating oats.

Grok was constantly say it was doing something that it had ZERO ability to, and I kept calling it out and it kept apologizing and then immediately doing it again.

As a guy who spend 5 figures a year on Ai, the last thing I want is that. I know Claude and ChatGPT also do it, but Grok was doing it CONSTANTLY.

And rightfully so, IMHO. The IA has legitimate goals for fair-use, but I don't think that fair use extends to bulk copying of an archive and for profit.

It's also my belief that the Internet makes it really convenient for outright theft of other intellectual property.

You can't have it both ways; kleptocracy is evil.

I know who the maintainers are and what their responsibilities and trajectories are. While no one was looking (Linus), lots of diverse platforms became supported. Provisions were made for both very progressive (if often never ever ever used) modularity.

On the app side, an enormous number of apps found their way inside, often stuff that users (remember users?) didn't ask for but they got The Big Gulp anyway.

I indeed wrote operating systems before Linus Torvalds was born. Wrote in Byte about Linux long ago. Watched a ton of operating systems grow and fail for want of a practical purpose or momentum.

I've surfed the wave of FOSS and Linux (and various BSD) developments for a long time. I have an engineers sense of less is better, and that attack surface involves anchoring unmaintained yet still distributed JUNK into fun attacks. Or watching users (remember users?) become dogged by sheer inode displacement.

Distros don't use Darwin as their set of choices, or even public demand for their content choices. They simply shovel in stuff. More is better. This policy is provably a poor choice.

The relationship between enabling interesting stuff in the kernel and the bloat of distribution apps is highly intertwined. The kernel and app payload enable each other.

Philosophically and relating this to the OP, bloat is bad. It eventually serves too many at the price of integrity and TCO.

Bullshit.

The kernel is built around features, resources, and libs that will touch it within the kernel. This 100% disciplines the "features" that distros shove in, often with seeming hydraulic pressure, into distributions.

Yes, it's a "Swiss Army Knife" with incredible flexibility. And it is a blimp. Then there are untold lib bloats to feed edge case use of distributions. It's my contention that you could slice the entire beast in half and still have great functionality for the bell-curve use cases.

I watch kernel development. There is so much goo inside the kernel that it no longer floats, it sinks under its own weight, and drowns the OS with barnacles and lead.

Like other seemingly simple solutions, this one is wrong.

The major distros have become unbelievably bloated, with Ubuntu leading the pack. LinuxMint needs ozempic in the worst possible way.

The kitchen-sink approach is just wrong and increases attack surface, while those having no choice but older hardware with fewer resources have to cringe.

Although lightweight versions are possible, the sheer sprawl of inodes has become ridiculous. No OS should need a half-million files installed from core executables and libs and sheer goo.

If you have to use W11, it's one more thing to add to your scrape script. This is a sorry last-ditch attempt to make Xbox relevant again. Easy scrape and joins the piles of crapware that doesn't belong in an operating system.

And Linux distros could go on a diet, too. Hey Linus, it's getting FAT.

This will not end well.

Why is this a problem?

I do not want my software censoring anything I make.

Zhao forgets what quality, supply chain, consistency, scalability, reliability and lifecycle worth mean. His remarks are self-serving, and facile at best-- and a symptom of a deeper disease that permeates capitalism: Cheap Tricks That Don't Work.

This is Darwinism at work.

Structure, revenue, stature in the rise of developer networks.

You forget that Microsoft built itself on its addictive developer network. They harnessed hundreds of thousands of coders into an army that developed much code, some good, some bad, some hobbled by Microsoft mistakes and bad business partnering.

Now Microsoft wants to bypass coders and admins and go direct. Direct to those that would become dependent on AI related contexts, each a silo, each a house of cards with unknown dependencies and life cycle.

The idea of traditional data processing safeguards gets tossed out the door with it. Even the madness of Microsoft run-times evaporates, because each bit of code is unique, and by definition, not homogeneous and lacking interoperability with other code. A million little bits of non-related code creates a wasteland of stuff that can no longer work. Who's going to fix THAT?

Neoliberalism and liberalism are two totally different things.

That's silly.

The largest objection is the panopticon, and people's nose in others business with out the warrant or need. Remember probable cause?

What about liberty and freedom? Freedom of association? Oh, wait, that must be another constitution.

Speed cameras, red light cameras, cameras in general need to go. Raise taxes, employ competent LEOs to give fat tickets for witnessed offenses. Soon, you're going to be convicted based on AI, which as a non-human, is unable to be challenged in a court because it can't be cross-examined. What of that constitution?

This'll happen while the kleptoclass are flying over you in their drones or private jets, as you battle the streets, waiting for you to spit, so you can be fined because you're the new profit center. Yes, you.