TensorMetric

6 ms·

31.
by TensorMetric 9y ago
Microsoft's own .NET Native runtime is simply not .NET compliant https://news.ycombinator.com/item?id=15007166 This is unacceptable and should be fixed ASAP. F# is a mature language existing for more than a decade, the
32.
by TensorMetric 9y ago
We should make a bigger fuss about F# support for UWP https://news.ycombinator.com/item?id=15007166
33.
by TensorMetric 9y ago
If only Microsoft would let us build native UWP apps in F# without having to jump through hoops with web frameworks https://news.ycombinator.com/item?id=15007166
34.
by TensorMetric 9y ago
It's because Microsoft's main client application platform's .NET runtime is not .NET compliant, resulting in their own language, F#, not be supported. See here https://news.ycombinator.com/item?id=15007166 Th
35.
by TensorMetric 9y ago
> After one year since has been flagged as WORKING ON IT , the support for .NET Native is not even in roadmap https://github.com/Microsoft/visualfsharp/issues/2400 . And see comments here https:/&#x2F
36.
After more than three years, still no F# support for .NET Native and UWP(wpdev.uservoice.com)
8 points by TensorMetric 9y ago|1 comments
37.
by TensorMetric 9y ago
See also comments here https://blogs.msdn.microsoft.com/dotnet/2017/07/24/get-start... > There is no timeline for F# support on UWP. If you must use UWP for your workplace, then F# is not an option fo
38.
After so many years, still no .NET Native nor proper UWP support for F#(github.com)
1 points by TensorMetric 9y ago|1 comments