4 ms·
> If a non-MS affiliated company marketed a language as lean as F#, with as good a runtime and editor/debugger, they'd be a huge amount of "hipster" cred and p
by Mikeb85 13y ago
> If a non-MS affiliated company marketed a language as lean as F#, with as good a runtime and editor/debugger, they'd be a huge amount of "hipster" cred and praise.
OCaml? Which is what F# is based on, compiles to anything (including fast native code), and is open-source?
- MichaelGG 13y agoAre OCaml's main libraries even threadsafe yet? Is there a smooth editor/debugger like Visual Studio? Just a quick look says the Windows version of OCaml doesn't even have a debugger. OCaml is neat, and more advanced than F# in some aspects, but I'm not sure the dev experience is nearly as slick. Another thing not mentioned: libraries. Anything half-well designed on JVM or .NET has access to a massive amount of libraries (and both stdlibs are pretty complete). Depending on the project, that's not a trivial consideration. More info from a biased source: https://www.quora.com/Functional-Programming/How-does-F-compare-to-OCaml/answer/Jon-Harrop-2?srid=OjRF&share=1 https://www.quora.com/Functional-Programming/How-does-F-comp...
- gaius 13y agoYou can get a fairly complete stdlib on OCaml too, as long as you are willing to commit yourself to using Jane Street Core rather than the one that comes with the language.
- nbevans 13y agoF# is open source too. </minor pedant>
- Mikeb85 13y agoThe runtime (.NET) isn't...
- MichaelGG 13y agoThe runtime is actually the CLI, which is a standard and has open source implementations.
- nbevans 13y agoI assume you're referring to the CLR here? As in: http://en.wikipedia.org/wiki/Common_Language_Runtime http://en.wikipedia.org/wiki/Common_Language_Runtime Whilst no, the Microsoft CLR is not open source. It doesn't need to be. Because the CLI is a ECMA standard and known-good third party implementations (Mono) already exist. The only thing to be gained from open sourcing the Microsoft CLR would be to benefit Mono. As Mono is the defacto official cross-platform port of the CLR. Since the Microsoft CLR almost certainly contains IP and trade secrets that they wouldn't want their commercial rivals to see, it would be more beneficial if Microsoft merely gave a fairly open code sharing and IP license to the Mono / Xamarin team so that they could benefit in the exact same way as though it were OSS MIT.
- profquail 13y agoI suspect F# can also be compiled to nearly anything OCaml can be -- that is specifically the point of the Code Quotations feature of the language. F# is also open-source (https://github.com/fsharp/fsharp https://github.com/fsharp/fsharp). Why do you keep implying it isn't?
- Mikeb85 13y agoThe .NET runtime isn't open source... I like how this is down-voted as though it isn't true...
- MichaelGG 13y agoPerhaps because you're being pedantic about .NET versus the CLI? The CLI spec is a standard and open source. Microsoft's own version isn't open source (well, they did release an "open" source version, Rotor). But Mono's is.
- profquail 13y agoCorrect -- the .NET runtime isn't open source. F# has a very strong following on Mono though. In fact, I suspect a higher percentage of F# developers develop and/or deploy on Mono than any other language does. You may not know this, but F# ships with the Mono distribution for OS X, and it may well ship with the Linux packages before long. BTW, I maintain the F# port for FreeBSD, and the combination of F#, Mono 3.2.x, FreeBSD 10, and emacs is extremely fast and stable. http://fsharp.org/use/freebsd http://fsharp.org/use/freebsd
- platz 13y agoI think the performance of Mono on Linux is a bit lacking though, compared to other Linux VM's/Runtimes or the Windows CLR runtime.
- profquail 13y agoThat's true. Mono is generally slower than the CLR, though it has been improving ever since Xamarin took over. There's also an option now to use LLVM as the JIT compilation engine in Mono; for server-based applications (where steady-state performance matters more than start-up time), this can greatly improve the performance thanks to LLVM's optimizer. With the improvements in the latest 3.2.x branch, I think Mono's performance is at least "good enough" for many use cases. FWIW, I do a bit of F# + Mono development on FreeBSD 9 (and now FreeBSD 10) and have found the performance to be quite good. I wrote an installation guide (http://fsharp.org/use/freebsd http://fsharp.org/use/freebsd) if you want to give it a try, e.g., in a VirtualBox VM.