TensorMetric

6 ms·

1. 1.▲
   by TensorMetric 8y ago

   https://www.thurrott.com/cloud/office-365/161295/microsoft-r...
2. 2.▲
   by TensorMetric 8y ago

   They are actually using Typescript, and this will lead to less friction wrt hiring devs, supporting all those platforms and integrating web components. Still I would have hoped that MS would be a little more forward thinking, and put some o
3. 3.▲
   by TensorMetric 8y ago

   Not wrong, see the Windows 10 OneNote app for example, which already uses Typescript on WinRT/UWP. An Electron target will only be for legacy platforms, like Windows 7 and 8. Also see https://www.thurrott.com/cloud&#x2F
4. 4.▲
   by TensorMetric 8y ago

   On Windows 10, they will target WinRT on UWP, with Fluent Design UI. Not Electron.
5. 5.▲
   by TensorMetric 8y ago

   > Why not C#? See my comments here: * https://www.reddit.com/r/programming/comments/8qqhlz/office_... * https://www.reddit.com/r/programming/comments/8qqhlz/office_
6. 6.▲
   by TensorMetric 9y ago

   To me and many early investors of F# (loyal Windows developers), the current direction is the worst thing that happened to the language. UWP is not just a nice to have, it's the backbone of client Windows development right now and goin
7. 7.▲
   by TensorMetric 9y ago

   As was stated before, UWPs primary device type is every Windows 10 device. https://np.reddit.com/r/Windows10/comments/75lgti/announcing... You don't seem to understand what UWP is about.
8. 8.▲
   by TensorMetric 9y ago

   The main device type for UWP is any Windows 10 device. See the list of benefits mentioned in the link above, which extend beyond phones. I've never owned a Windows Phone, yet I always prefer UWP apps. Also there is a big market for 2-i
9. 9.▲
   by TensorMetric 9y ago

   I've been holding of targeting UWP, until proper F# support. I have experience with plenty of languages and technologies, including C, C++, Rust, Scala, OCaml, Haskell, Clojure, Elm, Idris, WinForms, WPF, DirectX and dabbled with Silve
10. 10.▲
    by TensorMetric 9y ago

    Nothing is being moved. UWP has been here since the dawn of Windows 10, which evolved from WinRT, going back to Windows 8, and is constantly being extended with new APIs.
11. 11.▲
    by TensorMetric 9y ago

    UWP is the primary Windows client application platform going forward. https://np.reddit.com/r/csharp/comments/75mc1m/announcing_uw... All this FUD and hostility from the F# community (including the Fable
12. 12.▲
    by TensorMetric 9y ago

    That would require Microsoft, the F# team, and the vocal F# community members to actually want F# to be a proper first-class .NET citizen, which sadly isn't the case. https://np.reddit.com/r/fsharp/comments&#x
13. 13.▲
    by TensorMetric 9y ago

    This is minor compared to all the major things VS isn't shipping for many years in a row now.
14. 14.▲
    by TensorMetric 9y ago

    It's misleading to pretend that it's a substitute for full Visual Studio.
15. 15.▲
    by TensorMetric 9y ago

    It's only recommended temporarily, until the issues get ironed out. It doesn't make it THE first-class F# IDE.
16. 16.▲
    by TensorMetric 9y ago

    > You can gripe about your fav UI stack not being supported just the way you want (you don't seem to have any other complaints), .NET Native and UWP are not just UI, > but your claim the language is not improving is wrong. You&#x
17. 17.▲
    by TensorMetric 9y ago

    I'm surprised that this comment isn't at the top of this thread.
18. 18.▲
    by TensorMetric 9y ago

    All those features mean nothing to seasoned .NET developers when you can't use the language natively on Microsofts primary application platform.
19. 19.▲
    by TensorMetric 9y ago

    Nonsense, UWP is everywhere https://np.reddit.com/r/fsharp/comments/6tdrwq/after_so_many... https://np.reddit.com/r/fsharp/comments/6tdrwq/after_so_many... https:&#x
20. 20.▲
    by TensorMetric 9y ago

    Adoption of F# would not be a problem if it had .NET Native support and proper tooling https://news.ycombinator.com/item?id=15026396
21. 21.▲
    by TensorMetric 9y ago

    The first-class IDE for F# is the full Visual Studio, not VS Code + Ionide.
22. 22.▲
    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 We wouldn&#x27
23. 23.▲
    by TensorMetric 9y ago

    The real problem with F# is that it isn't supported everywhere C# is https://news.ycombinator.com/item?id=15026396
24. 24.▲
    by TensorMetric 9y ago

    Thanks this is great information. Have you looked into using Scala or Rust for UWP apps?
25. 25.▲
    Lack of .NET Native support for F# drives valuable developers away from Windows(np.reddit.com)

    5 points by TensorMetric 9y ago|0 comments
26. 26.▲
    by TensorMetric 9y ago

    I really can't stand C#. F# is what drove me to .NET in the first place. And I don't like going back to C++, is there any GUI/XAML tooling for it? If not, I'd rather use something like Rust.
27. 27.▲
    by TensorMetric 9y ago

    Also sad to see those members who liked his tweets.
28. 28.▲
    by TensorMetric 9y ago

    It also doesn't help when prominent members of that that community keep spreading FUD about UWP, driving more Windows developers away from F#. https://www.reddit.com/r/programming/comments/6tppt4/f_a
29. 29.▲
    by TensorMetric 9y ago

    If it's going to be fixed this year, then why isn't it even on the official road map? https://github.com/Microsoft/visualfsharp/issues/2400
30. 30.▲
    by TensorMetric 9y ago

    And still no proper F# support https://news.ycombinator.com/item?id=15007166 And another buggy release https://twitter.com/ReedCopsey/status/897125930195234817 Just like before https://