Re:State of Multicore OCaml [pdf]
by seanmcdirmid on Thursday June 28, 2018 @08:14PM
(#17421492)
WPF has been stagnant for a while, I think they just have a maintenance team on it at MS. UWP is where the new action is supposed to be, but it is limited to store apps.
F# is not compatible with UWP because .net native doesn’t implement the .tail IL opcode so it’s a no go. Moreover WPF allows a wider distribution that UWP which is restricted to Win10.
F# can be used to develop for UWP via ReactNative (Microsoft fork) and Fable compiler. Here's a cross-platform sample: https://github.com/elmish/sample-rn-counter
You can always disable tail calls via a compiler flag. I think the real issue is that .NET Native can't handle very deeply nested generics (although this may have been fixed). There are also issues with reflection in certain cases, but I believe they can be worked around.
Re:State of Multicore OCaml [pdf]
by seanmcdirmid on Friday June 29, 2018 @02:22AM
(#17422768)
True. But WPF is not going to be improved, it is just like WinForms now. UWP has all the modern API goodness (win2d, better rendering) while Microsoft seems to be pushing developers to web for everything else.
Starting a new project in WPF at this time doesn’t make sense.
Except that main feature of .NET Core 3.0 roadmap is to support Forms and WPF, while allowing mixing UWP controls on them called XAML Islands.
So they are getting some newly found love on their way to the store.
Microsoft has realised that the best way to force devs into the shop is to merge Win32 and UWP worlds.
Some links:
https://fsprojects.github.io/FsXaml/
https://github.com/Prolucid/Elmish.WPF
https://github.com/GtkSharp/GtkSharp
https://github.com/AvaloniaUI/Avalonia
https://github.com/xamarin/xamarin-macios