"Reliable Computing" and post-Redstone Windows


I’m sure most of us are familiar with Paul’s repeated call for a “reliable computing initiative.” This has me thinking about overall stability and reliability in Windows 10. I like the way Windows 10 works, and it has gotten better over time, but I am annoyed by a lot of the little inconsistencies and problems that continue to crop up. However, I’m interested what a reliable computing effort might look like beyond taking a break from the update stream in favor of some consolidated bug fix patches (I think that’s kind of what Paul has in mind?)

Some of you may remember the release of Apple’s Snow Leopard back in 2006. That release was billed as one focused on refinement and stability as opposed to adding new features. Of course, there were some very significant new features and changes, but they mostly served the goal of improving the base system rather than adding new capabilities. A good example is rewriting the Finder in Cocoa – this might be compared (imperfectly) to rewriting File Explorer in UWP or .NET to gain overall system stability. There are a lot of things like that that MS could put together in a new version of Windows – polish, stability, and future-proofing sorts of improvements.

Anyway, I’m curious in whether people think such an effort is needed, whether it’s likely, and what form it should take. Stop rolling out new versions or feature patches and just work on bug fixes for some amount of time? Make the next release (or two) of Windows after Redstone 3 focused on those things a la Snow Leopard but continue new releases? And what are some of the most-desired changes of that sort? Personally I’d love to see a concerted effort on this front, but I’m assuming that Redstone 3 is already set in stone as another feature-oriented release.

Post Reply