You make some good points, and some I didn't quite agree with. The notion that you could just recompile old win32 apps, while nice in theory is not practical IM

You make some good points, and some I didn't quite agree with. The notion that you could just recompile old win32 apps, while nice in theory is not practical IMO. Software has gone from being heavily GUI oriented (windows, dialogs, buttons) etc to converge into something between web and UI. I'd rather they make a clean cut with that past than incorporating it into the future. Also lots of new stuff like notifications, roaming notifications/settings etc are things that simply did not exist with traditional software. I do agree however that I miss some deep level win32/OS integration possibilities in the current UWP world, on the other hand there's lots of new cool stuff like App services, notification listeners etc. I agree completely that a big problem was the constant reboots between Zune/silverlight/NT/Win10. They ended up where they needed to be but it certainly made things difficult for both developers and consumers, and lost them a lot of momentum Supporting 512 mb devices was one of the biggest mistakes they ever made, the impact on that the development side was just devastating, for what, saving a couple of bucks in RAM memory? I think it's hard to generalize the speed and pace of Windows Mobile overall, they put a lot of money and effort in it, and still is, but something definitively changed with the Nokia acquisition and/or Nadella taking over from Ballmer As for updates I always got frequent updates (europe), the problem was more that their QA seemed substandard. Might be an american problem with providers like Verizon. They had an interesting strategy with their insider updates... which is nice in theory but it sometimes felt like they fired their QA team and put the burden of testing on their consumers, resulting in major bugs frequently getting through