A high price tag for a niche language (purely defined by "popularity") is hardly surprising, simple question of supply and demand.
F# Not just for finance
31–40 of 138 posts
Re: F# Not just for finance
#32Earlier 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
We have an almost identical setup to yours. How do you manage the long build chains in team city with the number of nuget packages you have? It's something we are grappling with and are considering moving everything back into a single repo with no nuget packages as a result.
Re: F# Not just for finance
#33Just tried F# on https://www.codingame.com/games/puzzles
Don't really see the use case for me, but fun to try smthg new => "one new language a day keeps the boredom away"
Re: F# Not just for finance
#34I was an early adopter of F# (1.0) and promoted it pretty heavily in my previous job. We used it for some of our prediction code. I've since left and move to the Linux world, but have become more involved with using OCaml. Both are great languages (probably my favorites) and that's after investigating Haskell for a while. F#/OCaml's ability to easily move between functional/procedural/OO worlds makes it super flexibl…
> F#/OCaml's ability to easily move between functional/procedural/OO worlds makes it super flexible.
When I wrote the reference compiler for an intro to compiler class in OCaml, some of the teams who used Haskell asked me about my choice; I said that while most of the compiler was written in a nice FP style, it was nice to have imperative constructs in a few places to follow the techniques from a textbook without having to adapt them and making sure that I haven't changed the complexity.
Re: F# Not just for finance
#35Earlier quoted context omitted.
What concurrency models do you employ to saturate all cores, and how's GC behavior?
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?
Re: F# Not just for finance
#36Earlier quoted context omitted.
Have you ever used Jet? Try it, add a few things to your cart then add a few more and see what happens to the prices of the previous items. There are millions of permutations being computed behind the scenes. The system is computing prices all of the time based on many factors. Plus we have built everything in house from our warehouse management system and supply chain tools to order management and everything else. T…
I haven't used Jet, no. I'm not trying to call you out, just wondered why it was so large. I have to deal with a similar amount of pricing complexity (actually, probably more complex than Jet) in my line of work, and we don't need anywhere near that amount of resource, but granted we don't have your numbers either, and our setup is much easier to silo groups of users - so probably not directly comparable.
I work at Expedia. The hotel dynamic pricing engine alone is more than 2200 cores.
And this is c++. It does handle a average of 200k requests per second though.
Don't underestimate true cpu intensive work.
Re: F# Not just for finance
#37There is an interesting article about rewriting C# project in F#, with impressive results:
http://simontylercousins.net/does-the-language-you-use-make-...
Re: F# Not just for finance
#38I'm quite sure KDB pays more.
Re: F# Not just for finance
#39Here is the Louvre Architect demonstrating the use of F# to help with the design of the structure: https://channel9.msdn.com/Events/FSharp-Events/fsharpConf-20...
Re: F# Not just for finance
#40any good tutorials for F#?