3 ms·
Not sure why this is getting downvoted I think it's dead on. Yeah desktop's always been fragmented, but it hasn't always been in today's state of utter neglect.
by m_fayer 7y ago
Not sure why this is getting downvoted I think it's dead on. Yeah desktop's always been fragmented, but it hasn't always been in today's state of utter neglect. Look at Windows - wpf was powerful, elegant, and ahead of it's time. Now it's abandonware with nothing to replace it (please don't say UWP). To reiterate - right now the world's dominant-by-a-mile desktop OS has no viable modern 1st-party native UI toolkit.
- pjmlp 7y agoI will say WinUI instead then. https://github.com/microsoft/microsoft-ui-xaml/blob/master/docs/roadmap.md https://github.com/microsoft/microsoft-ui-xaml/blob/master/d...
- Kipters 7y agoI wouldn't say WPF is abandonware, just look at the efforts to modernize it with .NET Core 3.0 (and as someone already pointed out: WinUI)
- m_fayer 7y agoAFAIK, those efforts are just trying to make it usable from Core 3.0 - they're not doing anything to address the verbosity and performance issues.
- Kipters 7y agoThey've also been doing work for making it easier to call WinRT APIs or introducing UWP controls (through XAML Islands) in both WPF and WinForms... A bit of a stretch, but this way they're both inheriting all the work they've done before for UWP. I think they also announced something about DPI awareness that won't be backported to classic .NET because it required runtime changes
- m_fayer 7y agoDoes any of that sound like it's even in the neighborhood of what's needed to you?
- Kipters 7y agoNot at the moment, I currently work as an iOS developer. But I'm working on a cross-platform app in my spare time (currently I'm only developing the iOS and Android frontends, while I ramp up the core), and when the time for the Windows frontend will come I'll probably pick WPF with XAML Islands when running on 10