4 ms·
> Something is very wrong with a business when a big proportion of the customer base is viewed as a burden on the product. The curse of products that are - in
by mschuster91 4y ago
> Something is very wrong with a business when a big proportion of the customer base is viewed as a burden on the product.
The curse of products that are - in their foundations - over thirty years old and used by billions of people. To expand:
- any time Microsoft does fundamental changes to the look and feel or to management/configuration, enterprise users (the kind that buys tens of thousands of licenses at a time, and there's a lot of these) get pissed because on top of having to pay Microsoft for new software (to avoid not getting updates for EOL software), they have to spend significant sums re-training employees, testing upgrade paths, rework internal tooling...
- if MS breaks too much or forgets to add compatibility modes/quirks, said enterprise customers are going to be pretty pissed because that can sometimes mean they have to buy new machines costing many millions of dollars (the market for hardware sporting actual parallel ports or ISA slots is insane, because so much early 90s hardware runs on that)
- at the same time, desktop Linux distributions and macOS keep iterating and innovating without having that burden. Linux userland generally doesn't care a bit about backwards compatibility, and Apple announces BC breaks early enough / keeps support long enough that users can upgrade over time - aided by the fact that most hardware that people attach to Macs doesn't cost more than ten to fifty grands (=very expensive audio / video stuff) and has to be upgraded anyway to keep up with new features. That in turn puts pressure on Microsoft to keep up with innovation.
- on top of that, technical baggage keeps holding back Microsoft as well. Apple ditched Intel long ago and now reaps the reward - mostly, no transistor space wasted with long-superseded crap dating back to the 1980s and way better power management - while Microsoft is more or less at the whims of Intel's mismanagement and the utter crap that third-party ARM SoC vendors throw onto the market and dare call a CPU.
- wolpoli 4y ago> if MS breaks too much or forgets to add compatibility modes/quirks, said enterprise customers are going to be pretty pissed because that can sometimes mean they have to buy new machines costing many millions of dollars The obvious solution is to leave those enterprise customers behind on the legacy edition of Windows and launching something new. But Microsoft seems incapable of going to market with something new also. They created Windows 10x, and then went and merged the new parts back into the legacy platform.
- kitsunesoba 4y agoIt's strange that MS has never did what Apple did with the OS 9 → OS X transition, starting with a fresh foundation and making a clean break from the predecessor by way of a well-integrated "Classic" mode that seamlessly runs legacy applications in a "borderless" VM. The most natural time to have done this would've probably been going from XP → Vista/7, which broke a number of old things anyway. For all that switching mainline Windows over to the NT kernel in 2k/XP improved Windows, the benefit wasn't as great as it could've been if they'd been able to unshackle the OS from backwards compatibility with all the preceding Windows/DOS stuff.
- wolpoli 4y agoWindows 10x was rumored to run Win32 programs within a single-combined container for backward compatibility purpose too.
- creatonez 4y agoKeep in mind that Apple didn't have much to lose, in the years leading up to OS X they were scrambling for market share lost to Windows 95, and already in a frenzy over a failed modernization attempt (Copland) that was intending to maintain backwards compatibility. They were truly desperate, on the verge of going bankrupt under a "corporate rehabilitator" CEO with no Steve Jobs in sight. Microsoft had a good thing going, with the massive success of MS-DOS and Windows 95 it was imperative that the next generation consumer OS, Windows 2000, could run programs from their existing well-respected platform without users noticing the gap. (With OS X, you noticed the gap -- totally different UI style when in Classic Environment, and the Carbon API for easy porting was a mess that went unadopted by developers)
- hakfoo 4y agoWindows 7 had that "XP Mode" feature where it would try to run things in a VM, but it was an unloved stepchild. Really, they could have done a lot better-- a VM jukebox with everything from DOS 3.3 onwards available could have made the "most compatible Windows ever"-- even old software that assumed a 4.77MHz CPU clock could have been rigged to run natively.
- bornfreddy 4y ago> - at the same time, desktop Linux distributions and macOS keep iterating and innovating without having that burden. Linux userland generally doesn't care a bit about backwards compatibility,... Well yeah, and we still don't see Linux on every corner (android excluded). Linux desktop is a joke. You can either pick DE whick breaks compatibility every now and then (Gnome, KDE, ...) or which has more or less stopped developing (Xfce). I understand, it is nicer developing new things than maintaining and evolving old codebases, but I don't think MS needs to worry about Linux in this segment. And I'm saying that as someone who actually prefers any Linux flavor to Windows.
- mschuster91 4y agoThe thing is, the Linux space at least has something nice and shiny to offer every now and then (although I'd say GTK and Gnome could go off and vanish and I wouldn't care). And it's not just UI where Linux keeps evolving. Just look at systemd - a fucking breeze to work with, whereas on macOS you're stuck working with plist's (annoying but OK), and on Windows it's literally the same crap from 30 years ago in the NT era. A Linux VM can do a cold start in well under 30 seconds, Windows needs anything from five to ten minutes and you can't optimize anything.
- psd1 4y agoWhere do you get "five to ten minutes"? I have a win11 VM that boots from cold to login screen in 10-20 seconds. Windows services can be configured with dependency order and with delayed start. There are startup profilers. I've seen and resolved slow boot times in misconfigured domains and with features such as roaming profiles. It's probably DNS ;-)
- mschuster91 4y ago> Where do you get "five to ten minutes"? I have a win11 VM that boots from cold to login screen in 10-20 seconds. Sorry, forgot to mention I'm talking about Windows servers. Desktop indeed has gone quite fast.
- wvenable 4y ago> at the same time, desktop Linux distributions and macOS keep iterating and innovating without having that burden. That's a bit of a re-write of history. Mac OS tried to throw away all backwards compatibly on day one but major software vendors told them to pound sand so they had to spend another year building out Carbon. Not to mention that Mac OS X itself is built on NextSTEP. Linux breaks front-end compatibility so much that never seem to make much progress on stability. > on top of that, technical baggage keeps holding back Microsoft as well. Apple ditched Intel long ago and now reaps the reward It's not technical baggage that is the problem. It's strategic issue. Microsoft had a fully functional build of Windows 7 for ARM a long time ago. The problem is they never just released an ARM version of their OS and let developers port their code to it. It was always paired with a new API, the windows store, a locked down version of the OS, etc, etc. This might be specifically to avoid pissing off their hardware partners. Windows NT was always multi-platform and they always made sure it would build and run on non-Intel CPUs. It has never been a technical issue.