Slashdot Mirror
Microsoft's Problem Isn't How Often it Updates Windows -- It's How It Develops It (arstechnica.com)
Ever since Microsoft settled on a cadence of two feature updates a year -- one in April, one in October -- the quality of its operating system (taking into consideration the volume of bugs that emerge every few days) has deteriorated, writes Peter Bright of ArsTechnica. From the story: The problem with Windows as a Service is quality. Previous issues with the feature and security updates have already shaken confidence in Microsoft's updating policy for Windows 10. While data is notably lacking, there is at the very least a popular perception that the quality of the monthly security updates has taken a dive with Windows 10 and that installation of the twice-annual feature updates as soon as they're available is madness. These complaints are long-standing, too. The unreliable updates have been a cause for concern since shortly after Windows 10's release.
The latest problem has brought this to a head, with commentators saying that two feature updates a year is too many and Redmond should cut back to one, and that Microsoft needs to stop developing new features and just fix bugs. Some worry that the company is dangerously close to a serious loss of trust over updates, and for some Windows users, that trust may already have been broken. These are not the first calls for Microsoft to slow down with its feature updates -- there have been concerns that there's too much churn for both IT and consumer audiences alike to handle -- but with the obvious problems of the latest update, the calls take on a new urgency.
The latest problem has brought this to a head, with commentators saying that two feature updates a year is too many and Redmond should cut back to one, and that Microsoft needs to stop developing new features and just fix bugs. Some worry that the company is dangerously close to a serious loss of trust over updates, and for some Windows users, that trust may already have been broken. These are not the first calls for Microsoft to slow down with its feature updates -- there have been concerns that there's too much churn for both IT and consumer audiences alike to handle -- but with the obvious problems of the latest update, the calls take on a new urgency.
This sounds like the Apple way
Depends... if we're talking iOS, you'd be spot-on.
MacOS (OSX) on the other hand? They got that stability/performance shit down fairly cold. My last MacBook Pro (5 years old, my wife inherited it last month, uses it daily) only got one OS re-install, and that was because I swapped out the old platter drive for an SSD not long after I bought it.
Zero stability issues, something like 5-6 OS upgrades on the same disk, a zillion patches/app-updates/etc... no sweat. Even today, it still runs as tight and fast as it did when I bought it in 2013. Only reason that I'm still not using it is because the 512MB GeForce in it doesn't run the Iray render engine worth a damn (slow old GPU, no RAM to speak of on it, etc.)
Quo usque tandem abutere, Nimbus, patientia nostra?
Not a question of marketing, I promise. The Iray render engine (built into a lot of CG rendering suites and apps nowadays) requires CUDA-enabled drivers, or else the render kicks to CPU for calculations, causing render times to go up by factors. This means a 30-minute render suddenly takes, say, an hour and a half... if you're lucky.
Microsoft's WHQL GPU/video driver has CUDA disabled, so you're stuck with CPU (not GPU) rendering - and you usually don't find out until after it begins. Also, when you have a 6-12GB GPU card, all that RAM goes to waste under Microsoft's driver. :/
Quo usque tandem abutere, Nimbus, patientia nostra?