4 ms·

A better (worse?) story is Windows Mobile 6.5, Windows Phone 7, Windows Phone 8, and Windows 10 Mobile all being completely different, incompatible platforms th

by tapoxi 7y ago

A better (worse?) story is Windows Mobile 6.5, Windows Phone 7, Windows Phone 8, and Windows 10 Mobile all being completely different, incompatible platforms that deprecated the prior one, before they decided to give up and use Android.

pjmlp 7y ago
And yet UWP still lives on, and is being improved to be independent of the actual Window 10 version, and to have Win32 and UWP on the same process.
gamblor956 7y ago
Not comparable. Microsoft stopped selling phones with those systems long before they stopped supporting them. They didn't just "turn off the servers" on those devices like Google has done with Nest. My old WM 6.5 phone still worked the last time I played with it.
- tapoxi 7y ago
  That's true, a better Microsoft analogue would be the Kin.
  - gamblor956 7y ago
    I don't see how the Kin is comparable. It was killed after just 2 months by both Microsoft and Verizon (it's exclusive sales partner) due to poor sales. Microsoft and/or Verizon also offered full refunds to the dozen people who purchased the device after MS announced it would be shutting down the Kin servers.
    - WorldMaker 7y ago
      The Kin was also the result of an acquihire situation and contractual obligations to release the product from the acquired firm.
- WorldMaker 7y ago
  Plus, there was a direct migration path at each phase. Someone doing .NET CF apps on WM 6.5 shouldn't have had that many problems converting their WinForms-ish mobile UI to WP7's Silverlight-flavored XAML, and the XAML differences between WP7, WP8, and WP10 seem all relatively minor compared to the overall compatibility base of the underlying .NET CF to "Silverlight" .NET "CF2" to proto-UWP .NET to UWP .NET. So many of the problems in those transitions were UX "best practices" changes and not anything technical. I know a lot of developers had problems at each step of that migration curve and that it wasn't as smooth in reality as it should have been (and was on paper), but calling each transition a reboot or a restart (or "completely different, incompatible") doesn't make sense when so many of the moving parts were the same and backward compatible with each other.

by tapoxi 7y ago

pjmlp 7y ago

And yet UWP still lives on, and is being improved to be independent of the actual Window 10 version, and to have Win32 and UWP on the same process.

gamblor956 7y ago

Not comparable. Microsoft stopped selling phones with those systems long before they stopped supporting them. They didn't just "turn off the servers" on those devices like Google has done with Nest. My old WM 6.5 phone still worked the last time I played with it.

tapoxi 7y ago
That's true, a better Microsoft analogue would be the Kin.
- gamblor956 7y ago
  I don't see how the Kin is comparable. It was killed after just 2 months by both Microsoft and Verizon (it's exclusive sales partner) due to poor sales. Microsoft and/or Verizon also offered full refunds to the dozen people who purchased the device after MS announced it would be shutting down the Kin servers.
  - WorldMaker 7y ago
    The Kin was also the result of an acquihire situation and contractual obligations to release the product from the acquired firm.
WorldMaker 7y ago
Plus, there was a direct migration path at each phase. Someone doing .NET CF apps on WM 6.5 shouldn't have had that many problems converting their WinForms-ish mobile UI to WP7's Silverlight-flavored XAML, and the XAML differences between WP7, WP8, and WP10 seem all relatively minor compared to the overall compatibility base of the underlying .NET CF to "Silverlight" .NET "CF2" to proto-UWP .NET to UWP .NET. So many of the problems in those transitions were UX "best practices" changes and not anything technical. I know a lot of developers had problems at each step of that migration curve and that it wasn't as smooth in reality as it should have been (and was on paper), but calling each transition a reboot or a restart (or "completely different, incompatible") doesn't make sense when so many of the moving parts were the same and backward compatible with each other.