7 ms·
The real problem with F# is that the .NET Native UWP runtime isn't .NET compliant, therefore doesn't allow F# code. See this link explaining the problem https:
by TensorMetric 9y ago
The real problem with F# is that the .NET Native UWP runtime isn't .NET compliant, therefore doesn't allow F# code.
See this link explaining the problem https://news.ycombinator.com/item?id=15026396 https://news.ycombinator.com/item?id=15026396
We wouldn't need to evangelize F#, if it just worked everywhere C# does with proper tooling support.
- toyotaboy 9y agoBarely anyone uses UWP. It's irrelevant.
- TensorMetric 9y agoNonsense, UWP is everywhere https://np.reddit.com/r/fsharp/comments/6tdrwq/after_so_many_years_still_no_net_native_nor/dlp0muc/ https://np.reddit.com/r/fsharp/comments/6tdrwq/after_so_many... https://np.reddit.com/r/fsharp/comments/6tdrwq/after_so_many_years_still_no_net_native_nor/dlpapbk/ https://np.reddit.com/r/fsharp/comments/6tdrwq/after_so_many... https://www.reddit.com/r/programming/comments/6tdqmv/after_so_many_years_still_no_net_native_nor/dlk0rl6/?context=3 https://www.reddit.com/r/programming/comments/6tdqmv/after_s...
- pjmlp 9y agoExcept for the people using Windows 10, developing with HoloLens, gaming on XBox ONE (after the latest firmware updates), or using Surface meeting boards.