3 ms·

From what I heard, they killed Astoria because there was fear no one would write UWP if it became good enough. The new Microsoft has pretty much given up on re

From what I heard, they killed Astoria because there was fear no one would write UWP if it became good enough. The new Microsoft has pretty much given up on real Windows development, so they're not afraid of Astoria in that sense any more.

pjmlp 6y ago
If that was the case they wouldn't be spending money on Project Reunion, React Native for Windows, Python on Windows (even hired Guido).
Lammy 6y ago
That’s how Blackberry 10 ended up for me. Very few native apps but lots of good FOSS Android ones that were just never perfect on the device. Overall poor experience that I wanted to love.
- dleslie 6y ago
  I still have my BB Classic kicking around somewhere. It's neat to load up for interests' sake because the app store and BB services are mostly still operational, and all the apps on the store are _free_; albeit, those apps which are wrappers around proprietary services tend to be grossly out of date. As a phone, it's still a better daily driver than my Pinephone. The camera is fast and decent, the audio is top-notch, it never crashes, and so on.
tasogare 6y ago
Nobody was going to develop for UWP anyway since (1) the community with knowledge of XAML and the app model was telling to fuck off with Windows Phone being shutted down (I was part of that community), despite its success in Europe, (2) Microsoft never sold any good amount of tablets to make the cross-device story believable and finally (3) UWP didn’t worked on the most deployed OS of the time... Windows 7. It never made any business sense to develop for UWP for a small market share when developing traditional app meant targeting almost every Windows machine out there. I think Microsoft did the exact reverse of what they had done: they should have open a cross-platform (OS X + Windows) store delivering Silverlight out of browsers app. The Mac App store never had a lot of success, there was a golden opportunity for Microsoft to bank on a concurrent platform.

pjmlp 6y ago

If that was the case they wouldn't be spending money on Project Reunion, React Native for Windows, Python on Windows (even hired Guido).

Lammy 6y ago

That’s how Blackberry 10 ended up for me. Very few native apps but lots of good FOSS Android ones that were just never perfect on the device. Overall poor experience that I wanted to love.

dleslie 6y ago
I still have my BB Classic kicking around somewhere. It's neat to load up for interests' sake because the app store and BB services are mostly still operational, and all the apps on the store are _free_; albeit, those apps which are wrappers around proprietary services tend to be grossly out of date. As a phone, it's still a better daily driver than my Pinephone. The camera is fast and decent, the audio is top-notch, it never crashes, and so on.

tasogare 6y ago

Nobody was going to develop for UWP anyway since (1) the community with knowledge of XAML and the app model was telling to fuck off with Windows Phone being shutted down (I was part of that community), despite its success in Europe, (2) Microsoft never sold any good amount of tablets to make the cross-device story believable and finally (3) UWP didn’t worked on the most deployed OS of the time... Windows 7. It never made any business sense to develop for UWP for a small market share when developing traditional app meant targeting almost every Windows machine out there. I think Microsoft did the exact reverse of what they had done: they should have open a cross-platform (OS X + Windows) store delivering Silverlight out of browsers app. The Mac App store never had a lot of success, there was a golden opportunity for Microsoft to bank on a concurrent platform.