Conversation

Notices

1. Verius (verius@community.highlandarrow.com)'s status on Saturday, 25-Aug-2018 06:38:27 EDT Verius
   Compared to a language like F# Haskell feels more at ease with itself. F# always has that awful mismatch between it's .NET side and it's functional side where you're thinking "should I use objects here and invoke this way or use functions and invoke that way". And, somewhat ironically, the tooling for Haskell seems at least on par with F# on Windows with free tools (i.e. no VS) and in some spots even better. I suspect that's because F# is and will be a secondary language in .NET with corresponding resource allocation while Haskell is it's own language with it's own support.
   1. Annah (maiyannah@community.highlandarrow.com)'s status on Saturday, 25-Aug-2018 12:26:37 EDT Annah

      in reply to
      @verius Pretty much every .net language feels at its worst with the .net part.
      1. Verius (verius@community.highlandarrow.com)'s status on Saturday, 25-Aug-2018 13:47:39 EDT Verius

         in reply to
         @maiyannah I have to disagree there. A language that's designed for .NET works wonderfully with it. However only one language is really fully and without compromise designed for .NET: C#. F# is awkward because there's an inherent conflict between the paradigms of the base lib and underlying type system and the functional style. C# doesn't have that mismatch and as a result works much better. VB.NET also doesn't have that mismatch but suffers from it's own problems (mainly design decisions for backward compatibility).