Hacker News Reader

Take F# for a spin. It offers nearly all of the type system tomfoolery one craves and all the tooling and nice-to-haves one wants. The big drag is that the async story and memory management aren't as big as a time vampire as Rust, so you do run the risk of actually solving business needs. I am sure some part of dealing with Microsoft can fill that void, though.

View on HN

Doesn’t f# require the .net virtual machine though? Most people I know picking rust like the fact that it’s compile to native code “always” and predictability and lack of random time of recovery from garbage collection

What does a VM mean to you? Because LLVM as a target is a VM of sorts too, and so is the memory model assumed by C.

I've been on the fence w.r.t giving it a try. How does it compare to Ocaml and haskell?

From a web point of view, you get full access to .NET, all the associated packages, and all the tooling. You start with a huge head start as opposed to Ocaml and haskell for that usecase.

It is Ocaml in all the ways that matter, but with .NET's async story/runtime/memory management, and tooling.

Reply on news.ycombinator.com