4 ms·
My dayjob involves a lot of Java, but the problem I'm working on seems to be a really good fit for a functional language. I've played around with Erlang, Elixi
by zeroc8 1y ago
My dayjob involves a lot of Java, but the problem I'm working on seems to be a really good fit for a functional language.
I've played around with Erlang, Elixir, Clojure and F#. The problem is that I'm always worried about getting stuck somewhere along the process and then end up regretting the decision to not use something more mainstream.
But F# seems to be a real beauty.
- yawaramin 1y agoIf your day job is Java, learn Scala 3. It will be a mind-expanding experience.
- throw234234234 1y agoGenerally you won't get stuck with F#, unless you would of got stuck with C# also. The escape hatch is there, with its pros/cons. The pro is mentioned - the con being that this is where F# gets im-pure and someone with experience would immediately have patterns/team standards to deal with the boundary/usage. C# libraries generally don't have this problem (e.g. Collections, Connection Libs/SDK's, etc) since you invoke them like any other function/object - C# frameworks which invoke your code (e.g. ASP NET Core) you typically need standard code patterns to allow most of your F# code to remain pure/simple. In general though I prefer the .NET runtime than the JVM in its current state - you can go a little bit lower level when required in hot code without going unsafe (value types, spans, etc).