Microsoft suspends development of touch-friendly UWP Office apps for Windows

Post by dep_b » Sun, Sep 30, 2018, 2:30 PM UTC

maxxxxx wrote: post #44

pjc50 wrote: post #16

Earlier quoted context omitted.

> The story is so bad Microsoft’s own flagship software has to build their own UI frameworks I think this might be the other way round: if they're not eating their own dogfood, it's much easier for the UI framework to come adrift from actual use cases. It's really telling that in Windows 8/10 they "modernised" some , but not all, of the control panel UI. It's basically random as to whether a setting you need will be…

"It's really telling that in Windows 8/10 they "modernised" some, but not all, of the control panel UI. It's basically random as to whether a setting you need will be in a Metro-flavoured window or a Win32-flavoured one." That's really infuriating. Makes me wonder what all these devs they have are doing the whole day. "To me, the trouble with everything after WinForms is that it lacks a really compelling reason to up…

Post by pjmlp » Sun, Sep 30, 2018, 2:34 PM UTC

GordonS wrote: post #38

pjmlp wrote: post #22

Earlier quoted context omitted.

I do Windows development since 3.0, currently maintaining a couple of Forms and WPF applications, the Forms are the hardest to maintain due event handling spaghetti code instead of proper MVVM with data binding, no use of Table/StackLayout components and still do background handling in BackgroundWorker classes.

How is the Visual Studio WPF designer these days? I worked on a WPF app around 5 years ago, and the form designer in Visual Studio was appalingly slow and quite buggy. I also wasn't a big fan of XAML - no matter how much time I spent using it, it mostly seemed more difficult and awkward to get components where you wanted them than with WinForms.

Post by pjmlp » Sun, Sep 30, 2018, 2:39 PM UTC

maxxxxx wrote: post #46

maxsilver wrote: post #33

Earlier quoted context omitted.

Microsoft shot themselves in the foot with UWP. It's actually pretty nice to write apps with it (in my personal opinion, anyway). But UWP only supports Windows 10. Very few commercial products are able to drop Windows 7 support (and like, literally zero enterprise products can drop Windows 7 support). So, no matter how nice UWP gets, most companies that would still be willing to write a native Windows app are 5+ year…

"Very few commercial products are able to drop Windows 7 support (and like, literally zero enterprise products can drop Windows 7 support)." You would be suicidial if you based any product you want to sell to business on UWP. Not only doesn't it Win 7 or 8 but I don't see in what way UWP is better than WPF.

Post by pknopf » Sun, Sep 30, 2018, 2:44 PM UTC

jcelerier wrote: post #34

threeseed wrote: post #14

Earlier quoted context omitted.

There is also Electron/Javascript. Skype/Teams are developed in it and they have invested a lot of effort into TypeScript.

There's also Qt which they used for OneDrive

Post by hawski » Sun, Sep 30, 2018, 2:53 PM UTC