Except that Steam houses thousands of games by various developers, not a small set of games built and designed by Valve. It would be pretty difficult, but not impossible, to remove that dependency.
Whether Valve should invest in developing technologies to keep Steam relevant is a business decision. This appears to be announcement of Valve's intent. I would not be surprised if paying off the technical debt incurred by Steam does not meet the investment model of Valve's controlling interests. The Windows ecosystem is littered with technically obsolescent cash-cows: e.g. Laplink.
[1]:https://msdn.microsoft.com/en-us/windows/uwp/packaging/packa...
Before Bring Your Own Device, there was bring your work home. Windows is to a meaningful degree a business class product sold to consumers. Removing sideloading from normal Windows would make Windows less attractive as a standard platform for enterprise if people cannot use line of business apps on any old device.
Of course, that doesn't make it irrevocable. But revocation seems unlikely to me.
False. With Windows 10, app sideloading is permitted by default.
Linkedin lists Valve as having between 200 and 500 employees. Putting a team of engineers to work on removing the dependency on Windows32 seems like a reasonable alternative to a course of inaction dedicated to letting Steam full into suck.
My intuition is that Microsoft is even likely to work with a partial potential competitor like Valve when it comes to something like this because anyone who is using Steam on Windows...well they're using Windows and Microsoft has an substantial interest in not having Windows suck for the people who use it.
To me, this kinda' sounds like Valve announcing that it's not really going to spend any more money on evolving the Steam code base.