All true, but simultaneously, if you look at it not in the “how did we get here” but “what’s out there today” light, it’s an option that can run on a lot of platforms. Not by some particular merit but because history happened this way - but that’s not a problem with the technology itself.
The article defines "success" in the Windows context as being "available everywhere". It does not address how it got to that point.
And sure, you might not like Microsoft, and you may not like how it became successful (using the above definition) but the fact that it is available everywhere is not in dispute.
Of course most successful things have murky pasts. We don't necessarily agree with how it got there, but there it is. That is, at least in the technical sense irrelevant. You may prefer LP's or CD's, but streaming is now the successful way to get your music.
That doesn't mean it's the only way though, and of course you are free to not use Windows programs, or play games via Steam etc. That is your choice.
Yep, it pulls stuff from at least npm, it’s not a secret - check the source code.
Actually it pulls latest versions (checking registry then installing that exact version, not sure why they sidestep normal resolution algorithms) no matter what .npmrc may say, so min-release-age breaks almost everywhere it integrates with JS/TS ecosystem (most visibly, Copilot). I probably should’ve filed an issue.
It also installs Go packages but I haven’t looked into that.
They have built an orchestrator, not Kubernetes. There is one key difference: they know this thing, end-to-end, down to every single bolt and piece of duct tape (with possible exception for Docker internals)
And that's a very important distinction when it comes to maintaining complex systems. This could've changed with LLMs (I'm still adjusting to what new capabilities mean for various decision-making logic), but before machine intelligence debugging an issue with Kubernetes could've been a whole world of pain.
And chances are only they know it. If my role has enough cluster access, I can muddle through pretty much any helm chart (with lots of cursing, yes) but it might take me days to set up whatever elaborate bespoke environment and script invocations are needed to replicate the current production setup maybe.
> This is a modern “oops, I ran DROP TABLE on the production database” story.
It's not that story, though. It's a story "oops, my tool ran DROP TABLE on the production database" (blaming the tool). At least I haven't heard people blaming their terminals or database clients as if the tool is somehow responsible for it.
We’d all wish it’d be so, doctor. Sometimes it’s as clean as biological systems - touch something somewhere, a different seemingly completely unrelated thing elsewhere breaks.
Even in the dawn of the era, where accumulated complexity was a while lot lower, we have tales of 500-mile emails and “magic/more magic” switch ;-)
Inferring things in a legacy codebase old enough to drink can be quite a challenge. And the way I get it, you folks are dealing with a multimillenia-old mess of layering violations - so no surprise first principles are tricky.
Indeed, but then not surprising. Russia haven’t ever had developed a mature democracy, it merely had a very brief chance at taking long road of becoming one, and everything went off the rails in just a decade or so. Kind of a handicap when it comes to keeping bloodthirsty politicians and siloviki in check.
At least that produces tangible value for the rest of us this way.
Current idea of sports is that athletes wreck themselves for mere performance value (and money to the people who set it up, with a bit trickling down to athletes for enabling it all). As far as I understand, nothing they directly do is otherwise reusable to anyone else.
I’d rather watch a live commercial for human enhancement industries. At least that’s something that eventually becomes available to everyone.
Nah, it's simpler. Microsoft just lost sense of UX and touch with the reality to their own internal management vibes.
Look at the Windows start menu. It used to be trivial to switch users. Two clicks, one to open the user list, another to switch - done. Now it's four: user panel, three-dots, switch user, pick user.
Look at the login sequence. They want their Windows Hello and they don't care if it works well or not - no way to get a pin or password prompt instantly, you gotta click three times (one to show a method picker, another to pick PIN entry, and lastly one to focus the goddamn field) despite no reasons to hide this UI.
It's not like they're trying to scam or sell user into something. It looks like some internal decision-makers that don't ever dogfood their decisions losing touch with the common sense.
Apple has that too, and this rot spreads elsewhere. But it's not intently malicious, a lot of things simply don't make sense - just total lack of self-reflection capabilities at the corporate level.
reply