Viewing profile — TensorMetric

https://www.thurrott.com/cloud/office-365/161295/microsoft-r...

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 tha…

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 …

On Windows 10, they will target WinRT on UWP, with Fluent Design UI. Not Electron.

> 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_... Also, they'r…

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 ba…

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 …

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 alw…

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, El…

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.

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# communi…

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.re…

This is minor compared to all the major things VS isn't shipping for many years in a row now.

It's misleading to pretend that it's a substitute for full Visual Studio.

It's only recommended temporarily, until the issues get ironed out. It doesn't make it THE first-class F# IDE.

> 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 cla…

I'm surprised that this comment isn't at the top of this thread.

All those features mean nothing to seasoned .NET developers when you can't use the language natively on Microsofts primary application platform.

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://www.reddit.com/r…

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

The first-class IDE for F# is the full Visual Studio, not VS Code + Ionide.

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.co…