4 ms·
F# does not need UWP support since MS have allowed ["desktop bridge" apps](https://github.com/Microsoft/visualfsharp/issues/1096 https://github.com/Microsoft/vi
by bonesss 9y ago
F# does not need UWP support since MS have allowed ["desktop bridge" apps](https://github.com/Microsoft/visualfsharp/issues/1096 https://github.com/Microsoft/visualfsharp/issues/1096) (which may or may not signal the unofficial death of UWP...).
The .NET native compiler has some issues with handling valid tail recursion MSIL commands IIRC - they're working on it.
F# will always come in second in the MS tooling wars.
Interesting, though, to follow the track record of MS techs that come in first in their tooling wars over the last decade... Maybe being a bit slow on the uptake of the "latest and greatest" EF, or Oslo models, or Silverlight, or WPF, or WCF, or dotnetcores new project format, or UWPs new APIs isn't the worst thing if you want your solutions to be supportable in production for a while.
- pjmlp 9y agoMicrosoft is pretty explicit that it is a stop gap to port applications to UWP. That has been their main message in any presentation about the Desktop Bridge. Always showing how an existing application gets packaged, followed by replacing Win32 legacy features with modern UWP ones. The track record of other tech giants is not much different, let alone the usual reboots on GNU/Linux desktop stack.