k_cieslak
Joined 11 years ago
Joined 11 years ago
This is not true for F#.
I do appreciate the efforts of the F# open source community has always made in maintaining an VF# team.
But i still like it and managed to create fancy stuff with it - Ionide, React.js + Material UI applications etc. Wouldn't recommend using it on production ( unless You want to commit really hard into FunScript project and probably fix lot of this stuff) - WebSharper is providing more complete, richer solution and commercial support if needed
Since VS Code is built not on top of Atom but on top of Electron[2] both projects share just "lower level" possibilities and will both build different abstractions layers on top of it. Unless VS Code team chooses to build very similar API to Atom one direct porting won't be easy.
F# has had opensourced compiler[2] (written in F#) before it was cool in .Net stack and for most tooling things we are using FSharp.Compiler.Services[3] project - which basically provides all features of F# compiler (and much more) as normal .Net library. Projects like Visual F# Power Tools[4] and Xamarin Studio F# support[5] are using it to provide very interesting F# IDE features.
Since Vim, Emacs, Sublime and Atom (even though Ionide is written in F# and compiled to JS we can't use all .Net libraries) don't have direct access to .Net assemblies, community have created FsAutoComplete[6] project which is just command line wrapper around FSharp.Compiler.Services and works as "standard I/O server" where we send requests (for example if user wants completion list) and get appropriate responses.
[2] https://github.com/Microsoft/visualfsharp
[3] https://github.com/fsharp/FSharp.Compiler.Service
[4] https://github.com/fsprojects/VisualFSharpPowerTools
[5] https://github.com/fsharp/xamarin-monodevelop-fsharp-addin
Also in context of cross platform development - there exists also F# yeoman generator which provides some nice templates for F# projects outside of VS.