Hacker News Reader

Yes, I started in OCaml but switched to F# for the last 3 years and will likely move back to OCaml when effects are mature (when lwt and async are snuffed out).

Being able to use C# libs is very nice but also it sucks that I don't have true null safety.

Who knows, maybe F# is always more performant than OCaml and it doesn't make sense to switch back.

View on HN

> when effects are mature (when lwt and async are snuffed out).

That's actually on the way right now. The main concurrency library which is designed for OCaml 5, eio, internally uses effects but doesn't require its users to be exposed to them. Users write code in direct style and don't need to care about internal implementation with effects.

F# is .NET, so you can have pretty fine grained control over memory layout, right? Spans, packed structs, 8/16/32/64 bit signed/unsigned ints, etc.

That stuff all gets a bit screwy in Ocaml, an int has 31 bits of information but is 32 bits in size, a record with two int 64s ends up being twice you expect, etc.

Reply on news.ycombinator.com