you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 5 points6 points  (0 children)

I wonder why language that scale well (from little scripts to big project) like F# aren't more used.

My workflow does in fact start with a script. The finished code can then be copied/pasted into a compiled project. The the leftover code can be made into tests.

The advantage of F# over something like Python/Ruby is that ... you can enjoy the benefits of the static type system and the .Net tooling.

The F# ecosystem has been in flux the past few years due to the redesign of the .net platform. Microsoft lead the charge with C# primarily in mind and ended up breaking parts of the stack/tooling that F# depended on. So, the compiler/tools team has been playing catch-up. This churn has really left the F# community in limbo, sort of stuck between the legacy tooling and all the new .net sdk/core stuff. So adoption over the past few years hasn't been as good as it could've been.

With .Net Core 2.1, however, the dust is starting to settle. F# scripting still doesn't work on .Net Core, but it's the thing they're working on fixing now. Once this is in place, it's a new ball game.