[looser]

I only read the slides, but at one point the author mentions that they've built an hybrid app using (Haskell + C#).

Next, the author mentions about several limitations that C# has and that Haskell has a much better approach.

So, why use C#? Why not only use Haskell?

[bos]

Our app consists of two parts: there's a client component that integrates into Outlook, and a server part that does all the actual heavy lifting.

The client-side code is written in C# because the .net APIs for Office are the easiest to deal with.

[taudelta]

He mentions that later on during the Q&A session

[tome]

Could you please repeat it here so we don't have to search? Thanks.

[dan00]

Their application is an extension of Outlook, which only has a dot.net API.

[tome]

I wonder why they didn't use F#.

[jamwt]

He answered that too: language maturity. He was unfamiliar with the .NET ecosystem in general, and the availability of help/expertise/examples etc was much greater for C# than F#.

[dan00]

Brian just didn't wanted to have another risk, because F# is less mainstream than C#.

[looser]

Ok, thanks.