Live data from Hacker News

F# Not just for finance

fsharp.tv

41–50 of 138 posts

Re: F# Not just for finance

#41
I think the article is spammy and has a clickbait title. Unfortunately reading and addressing the actual article on Hacker News is old-fashioned.

StackOverflow surveys, while interesting, are probably meaningless because they suffer from selection bias. Even so, I would guess that F# developers are very well paid, like other developers of FP languages, but it's probably not because they work with F#. The causality is likely reversed - good developers that tend to be well paid are also the kind of people naturally interested in expanding their skill set, hence interested in FP languages.

Nothing screams spam more than usage of a hot keyword like "functional programming" while leaving hints that you don't understand what you're talking about. I would expect an article that reads like a marketing brochure to at least make a short attempt at explaining what functional programming is. If you copy/paste testimonials from fsharp.org/testimonials, you could also copy/paste from Wikipedia. But then, their own course named "Functional Programming" doesn't seem to have anything to do with actual functional programming: https://fsharp.tv/courses/functional-programming/

Re: F# Not just for finance

#44
post #18

Is anyone using F# on Linux? How's the experience?

I'm running it in prod since last year and from the runtime perspective there are no issues. Tooling is what sucks. MonoDevelop F# support is very unreliable. Basic refactoring, like rename, don't work correctly every time and I had to literally do git reset few times, after renaming, as it screw up multiple files. Also, editor often has visual glitches where letters get corrupted and I have to reopen the file to get…

Xamarin Studio and MonoDevelop are the same, what your probably seeing are the artefacts or using an old version of MonoDevelop

Re: F# Not just for finance

#45
post #44

Earlier quoted context omitted.

I'm running it in prod since last year and from the runtime perspective there are no issues. Tooling is what sucks. MonoDevelop F# support is very unreliable. Basic refactoring, like rename, don't work correctly every time and I had to literally do git reset few times, after renaming, as it screw up multiple files. Also, editor often has visual glitches where letters get corrupted and I have to reopen the file to get…

Xamarin Studio and MonoDevelop are the same, what your probably seeing are the artefacts or using an old version of MonoDevelop

I'm using the latest stable release of MonoDevelop (5.10)

Re: F# Not just for finance

#46
post #35
post #21

Earlier quoted context omitted.

F# has fantastic concurrency support. Great support for Asynchronous operations and Multi Threading. Being a functional first language and immutable by default means most of the micro services are stateless and this means we can take advantage of concurrency like crazy and not worry too much about race conditions. I think functional languages in general make concurrency much easier not just F#. GC on the other hand i…

I should have been more specific in the question. I'm used to Erlang and Haskell (GHC) concurrency primitives and frameworks. To reformulate: what concurrency models can you employ in F# that don't involve manually managing threads/processes?

Futures, for one (called Tasks I think). There are probably implementations of other models as well, but I never looked for them personally.

Re: F# Not just for finance

#47
post #19

Earlier quoted context omitted.

Small note about Nuget, you might consider upgrading to paket (works nice with C# too): http://fsprojects.github.io/Paket/ It removes so much pain compared to raw usage of Nuget and is very easy to learn/adopt.

> It removes so much pain compared to raw usage of Nuget and is very easy to learn/adopt We have a very large number of projects and migrating them all to paket would be a hassle, so I'd be interested in what pain in particular it removes? I'm no fan of nuget I can tell you, but I'd be interested to understand what you feel the big wins are

it is a worth to try. It is: - fast, - reliable, - understands transitive dependencies, - can manage them in groups (like build-deps, test-deps, doc-deps) - can have http and github as a source. Just one drawback - comparable not so good graphical UI in VS, but very good CLI, converts entire solution from nuget with just one command in terminal

Re: F# Not just for finance

#48
post #18

Is anyone using F# on Linux? How's the experience?

It works, although from what I recall the installation wasn't that easy. I think I had to checkout a specific tagged commit instead of the newest master, because the latter had a broken build. Probably works now, it was years ago :)

Re: F# Not just for finance

#50
post #35
post #21

Earlier quoted context omitted.

F# has fantastic concurrency support. Great support for Asynchronous operations and Multi Threading. Being a functional first language and immutable by default means most of the micro services are stateless and this means we can take advantage of concurrency like crazy and not worry too much about race conditions. I think functional languages in general make concurrency much easier not just F#. GC on the other hand i…

I should have been more specific in the question. I'm used to Erlang and Haskell (GHC) concurrency primitives and frameworks. To reformulate: what concurrency models can you employ in F# that don't involve manually managing threads/processes?

If you want to use an Erlang-style actors in F#, you can use Akka.NET:

http://getakka.net

Post reply on HN