3 ms·

Or even F#, which is basically OCaml on the CLR. Very fast, fully supported IDE, great if you're stuck in SLAs for CLR code, complete interop with C# or VB.NET,

• quim05 13y ago
  .NET sucks. Microsoft sucks. Take your transparent Microsoft advocacy elsewhere please.
• pjmlp 13y ago
  Pity that Microsoft pushes it more for library code and not so much for full applications. But if it gets more use in the mainstream that way, then so be it.
  • profquail 13y ago
    The only difference between a "library" and a "full application" is that the "full application" has an entry point where execution begins, whereas a "library" does not. Many large applications are implemented as a thin user interface (GUI, web, services/APIs) which glues together a bunch of libraries (which is where all of the real functionality is implemented). This doesn't only apply to F#, but C#, Java, Python, etc. The reason F# gets used for implementing libraries is because that makes it easier to introduce into organizations with existing code in C# or VB.NET; a new component or plugin can be written in F# and easily utilized by the existing code, so the other developers in the organization don't need to anything differently than if they were consuming another C# or VB.NET component.
    • pjmlp 13y ago
      I do understand the reasoning behind it, just as a ML fan would like to see the possibility of proper support for GUI/Web for pure F# applications. But I fully understand it, on my enterprise world JVM == Java and .NET == C#, except when doing small prototypes. It is very hard to use alternative languages, as managers always look for coding drones.