Re: F# fsharp

>
> Since you like toasty comments... why are Mono features
> important to a Windows developer?


I am not sure if you are genuinely interested in an answer of if you are
trolling as usual.

So let me preface my answer with the fact that I have not surveyed every
Mono user on Windows and that my answer is limited to what some developers
have chosen to share with me.   And it is not even statistically
significant, which means that you will likely troll the answer.

There are some minor technological benefits (Mono's SIMD support, Mono's
coroutines) but it seems that the one strength that Mono has on Windows is
that you can ship it embedded in your application and you get to choose how
much of it you need.   You can start at a very coarse level by picking and
choosing at the library level or at a finer level by removing code that you
do not use either by hand or with Mono's linker.

The embedding tends to be used for zero-configuration deployments, with no
dependencies on the registry, and be fully contained, like a MacOS
application.

Some users moved from OSX or Linux to Windows and they used Mono's embedded
APIs, so when they moved to Windows, it was easier to keep using Mono than
have to support two embedded APIs (.NET's and Mono's).


> I RTFM for plenty of MS docs.  I'm
> not aware of the mainstream, higher performance implementation of C#
> having a canonically supported interpreter.
>

C# produced CIL code, the code generated by Microsoft or Mono's compiler is
practically identical and there is no performance difference in the output.

The performance difference comes from the CIL execution system, Microsoft's
CLR vs Mono's VM and you can use our compiler on top of their VM for either
batch compilation, "eval" or the interactive REPL.

Miguel.

_______________________________________________
Sweng-Gamedev mailing list
[email protected]
http://lists.midnightryder.com/listinfo.cgi/sweng-gamedev-midnightryder.com