3 ms·
In my opinion it's honestly the best statically typed general purpose programming language. f# and also Ocaml strike for me the right balance between practical
by Barrin92 8y ago
In my opinion it's honestly the best statically typed general purpose programming language.
f# and also Ocaml strike for me the right balance between practicality and correctness (strict by default, no insistence on purity), but still immutable, good concurrency story, functional first with the ability to write imperative code easily, great type inference etc..
Given that so many mainstream languages are piece by piece moving into the same direction and adopting the ML family approaches I have no idea why not more people are moving directly to F# or Ocaml.
- laylomo2 8y agoI moved directly from Python to OCaml and I have to say, I’ve never been happier. Special shout outs to Jane Street, as their open source software is really solid and a pleasure to use. The community is small but really smart. Overall I think F# and OCaml really nailed the programming language design sweet spot of powerful and practical.
- grdvnl 8y agoCan you eloborate on what kind of projects you work on which has made the move easy from Python to OCaml. While I love OCaml I have not heard positive things about the library eco-system in terms of variety and maintenance. Perhaps, you could throw some light on that based on your experience, especially after giving up the eco-system Python provides you. This is a sincere question and would love to find good excuses to adopt OCaml as my primary language of choice.
- ernst_klim 8y ago>I have not heard positive things about the library eco-system OCaml has quite a neat ecosystem, though. Especially in terms of quality. There are a few major and a bulk of minor groups that write libraries for different purposes, such as: * MirageOS -- people behind a bunch of a high quality system libraries, there are tls (in pure ocaml) and various cryptography primitives, filesystem drivers, tar, zlib, full tcpip stack, http server, git (in pure ocaml, not a mere binding), irmin (a git-based key-store database with concurrent access), dns and some other [1]. * Ocsigen -- webdevs, authors of Lwt (monadic concurrency library), js_of_ocaml (ocaml to js compiler) and related stuff [2] * Jane Street, Facebook, blumberg -- reason syntax, bucklescript (alternative npm-ecosystem-frienly javascript compiler), various libraries for serialization, containers etc. * Others Opam [3] has quite a comprehensive set of libraries pretty for every purpose: data serialization, interaction with other langs (python, R, beam Erlang/Elixir), servers, db bindings, stuff for system or web programming. Some stuff is absent, but it's definitely not a scorched field, and most of the time the benefits worth writing an absent binding or two. [1] https://github.com/mirage https://github.com/mirage [2] https://github.com/ocsigen https://github.com/ocsigen [3] https://opam.ocaml.org/packages/index-popularity.html https://opam.ocaml.org/packages/index-popularity.html
- delhanty 8y agoI'm looking at Ocaml again because of the existence (and quality) of the Bucklescript backend for Javscript. That makes Ocaml sound pretty attractive on the portability front. A question for anybody here regarding portability: Is it viable to maintain a portable core using a subset of Ocaml (something like Standard ML maybe - no objects) and compile that in F# using Ocaml portability mode? For context, I've read this question on SO from 2010 [0] but I'm looking for some more 2018 perspectives from HN people. [0] https://stackoverflow.com/questions/4239121/code-compatibility-between-ocaml-and-f https://stackoverflow.com/questions/4239121/code-compatibili...
- nv-vn 8y agoMost likely not. You could get away writing a lot of utility type functions between the two, but the libraries, async scene, module system, object system, etc. vary enough that it would be practically impossible to share any non-trivial piece of code. Which isn't to say that porting anything would be hard, most of the core code would stay there and you'd only really adjust the edges of your code so to speak--if you separate out access to libraries or try to port the APIs from one language to another (which would be easy in OCaml with it's module system) it would certainly be possible to share 90% or more of your core code. But for example, you'd have to avoid using async/await in F# and instead opt for some library that has surface-level compatibility with OCaml's Async or LWT and working with .NET libs would require you writing wrappers for the OCaml standard library.
- delhanty 8y agoThank you. >it would certainly be possible to share 90% or more of your core code. It sounds like maintaining parallel code bases in Ocaml and F# with the same basic design and file layout might work quite well for the core.
- yawaramin 8y agoThat answer hasn't changed, in fact as of today OCaml and F# have diverged more than they had back then. BuckleScript and ReasonML are solid for the frontend, though. I would recommend them without hesitation. For the backend, F# could be nice but as I mentioned, you would share almost nothing between them. If you're looking for a universal (i.e. same language on BE/FE) stack there are many options today, but a classic one is https://ocsigen.org/eliom/ https://ocsigen.org/eliom/
- nikofeyn 8y agoi agree. f# is really nice and is very practically designed. it has very clean and consistent syntax. i wish more python people tried it. due to oop being perfectly fine in f#, one could write code in f# just as they do in python, and it would be superior in nearly every way.
- knocte 8y agoTBH I think F# wins over OCaml just because of its mobile deployment story. It doesn't seem that OCaml's ecosystem has mature solutions for iOS&Android deployment.