14 ms·
Good comment. Didn't realize F# let you have inline functions, everything as an expression and partial application. Forgot about pattern matching too! I don'
by runT1ME 13y ago
Good comment. Didn't realize F# let you have inline functions, everything as an expression and partial application. Forgot about pattern matching too!
I don't really see a need for workflows, I can do everything I need to use workflows for with custom LINQ.
I'll reconsider pushing F# for some of the c# work I do. However, if someone isn't bound to the CLR, i'll ask what F# gives you over Scala :-)
- MichaelGG 13y agoWithout workflows, you can't achieve e.g. async without building it into the compiler. You can abuse the LINQ syntax to simulate part of it, but you don't get proper exception handling, and it reads terrible as well. Versus Scala, F# seems far more concise. Scala seems to be very Java/OO oriented, and comparatively verbose. I understand the type system is more advanced in Scala. But I've not written anything in Scala so this is sorta speculation. I'd be surprised to find that the tooling for Scala surpasses F#'s though.