Re:Haskell typeclasses: Classes, Jim, but not as we know them
by tomh- on Friday November 25, 2011 @04:53AM
(#3276709)
Microsoft is the employer of two of the developers for the GHC compiler. Microsoft certainly has technologies related to Haskell such as F#. Also, a lot of the ideas for the new features of C# are based on the research and experience they've gained with Haskell. Linq, Lambda's, Task Parallel Framework etc.
Re:Haskell typeclasses: Classes, Jim, but not as we know them
by riffraff on Friday November 25, 2011 @06:46AM
(#3276864)
also in the other direction! Simon Peyton-Jones and Phil Wadler wrote a paper where they basically backported (and improved on) some LINQ features in haskell's list comprehensions: http://research.microsoft.com/en-us/um/people/simonpj/papers...
Re:Haskell typeclasses: Classes, Jim, but not as we know them
by tikhonj on Friday November 25, 2011 @05:10AM
(#3276737)
MS does have some technology related to Haskell (F# comes to mind immediately). However, I think Microsoft Research is also fairly academic--they are an actual research institution rather than an R&D lab. They are not at all afraid of very theoretic research with little regard for short-term profit. Which is really awesome.
Re:Haskell typeclasses: Classes, Jim, but not as we know them
by masklinn on Friday November 25, 2011 @06:04AM
(#3276811)
> Does MS have any technology related to Haskell at all? Or is it just research for the sake of it?
It's mostly for the sake of it, although some has trickled into F# and C#. MSR is the employer of two primary GHC developers (including SPJ, who's giving this talk), it's an organ quite similar to Xerox's PARC or Bell Labs: it does core research which may or may not be marketable in the long run.
Does MS have any technology related to Haskell at all? Or is it just research for the sake of it?