>>> Heck, even a regular expression match isn't functional in .NET.
>>
>> Probably. In fact, I doubt much of the .NET libraries are. So you would
>> probably end up using existing Haskell libraries for anything except
>> actual I/O - the thing that .NET is good at.
>
> I think .NET is good at more than just I/O. :-) Actually, I don't think
> .NET is any better at I/O that anything else on Windows is.

Well, I haven't ever used .NET, so I couldn't say.

>>> And that's the kind of incompatibility I'm saying makes .NET much less
>>> useful.
>>
>> Certainly it makes it less useful, yes. Whether it makes it "not worth
>> it at
>> all" is more open to debate.
>
> It breaks a fundamental tenet of .NET, which is that it doesn't matter
> what language the caller is written in vs the callee. MS saying that
> "yes, this .NET library works, but only if you call it from Haskell and
> not C# or VB or F#" would not fly well.

Well, another possibility would be "you can use this library, but it's 
up to you to not do any I/O within transactions. If you do, anything 
could happen, and it will be Your Fault."

Post a reply to this message