News for hackers. Stuff that matters.
Re:Announcing the F# 3.1 Compiler/Library Code Drop by gaze on Tuesday December 03, 2013 @02:21PM (#6842442)
Grrr. Why won't Microsoft open the CLR? It's so fast and has such amazing codegen! I don't want performance to degrade moving from Windows to some platform that requires I run mono!
Re:Announcing the F# 3.1 Compiler/Library Code Drop by dragonwriter on Tuesday December 03, 2013 @02:25PM (#6842488)
> Why won't Microsoft open the CLR? It's so fast and has such amazing codegen!

Watch how you are about to answer your own question.

> I don't want performance to degrade moving from Windows to some platform that requires I run mono!

Yes, but Microsoft, who sells Windows licenses, does want performance to degrade when you move from Windows to some other platform.

Re:Announcing the F# 3.1 Compiler/Library Code Drop by marshray on Tuesday December 03, 2013 @08:54PM (#6844521)
While it's not the same insanely-optimized JIT-compiled runtime implementation that you're asking about, note that the .Net micro framework has been released as Apache 2.0.
Re:Announcing the F# 3.1 Compiler/Library Code Drop by lucian1900 on Wednesday December 04, 2013 @05:25AM (#6846043)
The solution is to ignore .NET entirely and only use Mono, even on Windows. Then you get the same platform everywhere, as you would with the JVM.