5 ms·
You mean the old Microsoft? The new Microsoft just cancelled UWP. Their latest attempt to scare the hell away all developers.
by panpanna 7y ago
You mean the old Microsoft?
The new Microsoft just cancelled UWP. Their latest attempt to scare the hell away all developers.
- pjmlp 7y agoThat is plain FUD spread by anti-UWP crowd. UWP is alive and well, just go check the BUILD 2019 sessions. Apparently some keep missing the point that all new Windows APIs are based on UWP. There is much so more to UWP that the store. The only thing that are doing is bringing the legacy stacks (Win32, Forms, WPF) and the modern one (WinUI, UWP) under the same umbrella.
- deleted 7y ago[deleted]
- panpanna 7y agoRemember xna? How about Silverlight? Where is Windows Phone? You see, they don't have the courage to admit defeat. Just let it die and pretend it never existed.
- coldtea 7y ago>How about Silverlight? Where is Windows Phone? Those never got any traction to begin with. If people aren't using it, they wont miss it.
- panpanna 7y agoActually, they were fairly popular since they were the only viable option on certain platforms. Guess what happened to those platforms?
- ptx 7y agoPeople certainly did use it and are now suffering the consequences. The admin GUI for one popular CRM system is written in Silverlight – a natural choice since the rest of the system uses Win32, COM, .NET and pretty much every Microsoft technology you can think of from the past 25 years. Their new from-scratch rewrite is based on Python and web standards.
- pjmlp 7y agoYes, two victims of the WinDev vs DevTools internal wars pushed by Synfosky, with such a result that he ended up resigning. UWP was the fix to WinRT and UAP changes introduced by Sinosfky's team. Again, UWP is not only for Windows Phone, all Windows 10 new APIs are UWP based, there isn't any Win32 version of them. People are able to keep using their legacy skills to write new apps, because Microsoft seldom plays an Apple move, killing any possibility to keep using legacy stacks on modern OSes. If you miss XNA you can go use MonoGame, which Microsoft even advises on MSDN nowadays. And Blazor for Silverlight like use cases.
- panpanna 7y agoDo you realize what you just shrugged of more or less killed Windows phone??? When WP needed 3rd party games to have a chance in the consumer market Microsoft killed their fully functioning and very popular xna platform without explanation. For a while there was no replacement and the standard response from Microsoft was silence. Later Microsoft pointed to mono as a replacement. At that time, mono was slow, buggy and incomplete. In fact, for a long time mono was missing the asset pipeline tools. According to their official tutorials you had to dig up an old copy of xna and use their asset tools.
- pjmlp 7y agoI still own two devices, yes Microsoft failed to capture the market, even though they managed to achieve around 10% in Europe. UWP was never about Windows Phone only, rather Windows Phone, HoloLens, XBox ONE, 2-1 devices and Windows 10 desktops. So Windows Phone failed, plenty of scenarios still available on Windows 10 deployments.
- scarface74 7y agoAnd the number of companies who care about any of those platforms are vanishingly small. How many companies that still care about the desktop at all are going to invest resources in Windows only frameworks and not something like Electron? How many of those that are writing native Windows apps are going to use UWP instead of Win32?