Show HN: FUSE filesystem for Google Drive written in OCaml

That is a proxy on GAE that makes it easier to complete the OAuth2 flow. The source code of the proxy is here: https://github.com/astrada/gd-ocaml-auth. More info about the authorization process: https://github.com/astrada/google-drive-ocamlfuse/wiki/Autho.... Let me know if you need further info.

Probably the most known group using it in the US is Jane Street.

https://ocaml.janestreet.com/

In Portugal I would say it doesn't exist...

But I have knowledge of its usage on some projects by big corporations.

It seems that janestreet [1] takes great pride in using OCaml. They have some interesting open source projects in github [2] and bitbucket [3].

And facebook has pfff [4], an "Ocaml API to write static analysis on source code" (such as PHP code, not only OCaml code).

(I'm not a facebook or janestreet employee)

[1]: http://janestreet.com/

[2]: https://github.com/janestreet

[3]: https://bitbucket.org/janestreet

[4]: https://github.com/facebook/pfff

I can't speak to other undergraduate programs, but it's taught as the second course in Computer Science (Intro II) at Harvard College [0]. That said, it was chosen because it was less popular than other functional languages (namely Haskell or a Lisp flavor), so everyone was likely to be starting on "equal footing."

Take a look at the OCaml success stories [1]. Unison [2] in particular stands out—it's essentially the only two-way rsync tool for Unix, and it's written entirely in OCaml.

The only corporation I know of that uses OCaml is Jane Street Capital [3][4]. They've been huge proponents since they switched over, but the movement doesn't appear to have caught on among many other US-based companies. (More complete list [5].) Jane Street recruits fairly heavily from Harvard for internships—presumably because very few schools teach OCaml.

[0] http://cs51.seas.harvard.edu/

[1] http://caml.inria.fr/about/successes.en.html

[2] http://www.cis.upenn.edu/~bcpierce/unison/

[3] http://janestreet.com/technology/

[4] http://janestreet.github.io/

[5] http://ocaml.org/companies.html

In Italy it isn't popular at all, but a couple of friends of mine use OCaml, mostly for hobby projects. And I like the language. It is more advanced than main stream languages I know (C#, Javascript), but, being strict, it is easier (for me) to reason about than Haskell.

OCaml sees a lot of use in the applied program analysis community, which has applications to automated reverse engineering and formal verification. A company in this area recently started by CMU assistant professor David Brumley is: http://www.forallsecure.com/mayhem.html.

you learn it in the PL class at UMD (that everyone takes) and the compilers class (which is an elective) uses it for everything.

F# is a superset of OCaml and both are descendants of ML (ML was created here in Edinburgh). Having worked with Ocaml extensively I would say that the ecosystem around the language is pretty stale: the standard library sucks, as does the documentation for it and important libraries such as "batteries included" are under the GPL, which rules out many uses. Usability is poor: stack traces can be a nightmare to get working properly, the compiler errors are the worst I have ever encountered anywhere (including C++ templates!), there's no standard build chain, the list goes on...

I switched to Scala and haven't looked back. Haskell is very popular here in Edinburgh also.

I think it's relatively popular in University courses on compilers and programming languages. We use it for our Programming Languages and Translators course (i.e. the course the Dragon Book was written for) here at Columbia University.

University of Illinois uses it for CS421 "programming languages and compilers" (or at least they used to, and I'm assuming it won't have changed).

We don't use it at work, and I haven't heard any mention of it (or any other functional languages) at the various local programmer groups I recently started going to.

University of Illinois teaches it in the Programming Languages course: http://courses.engr.illinois.edu/cs421/mps/index.html

Back in when it was CS 321, the course used bison and ocaml to build a smaller ML language, which helped in understanding ocaml itself!

It is a compiled language with some decent enough unix integration, so this isn't the first system-level program I've seen written in it. The rather popular unison file synchronizer is Ocaml, too, if I'm not mistaken. For a while the most popular Linux client for the edonkey peer-to-peer file sharing network was mldonkey. And just recently I stumbled across a minimal PDF viewer called llpp that turned out to be Ocaml, too.

You can easily distribute packages without huge dependencies, it's not any worse at concurrency than your usual Unix go-to language C, and the FFI ain't half bad, either. It's also relatively unopinionated about IO, which certainly helps writing servers and system utilities.

There's also parsers and some web stuff, but I'll let others talk about this. Just wanted to say a bit about this somewhat surprising niche where the language managed to eke out a bit of a marketing share.

It's used in Cornell's intermediate-level, required, notoriously difficult functional programming course.

It isn't widely used here in the USA, in my experience and outside of people who are big fans of ML and derivatives, or those who had some OCaml exposure in college courses, most programmers here seem to be largely unaware of it.

I'm aware of it primarily through my exposure to Nicolas Cannasse's Haxe language, the compiler for which is written in OCaml.

On my team at Bloomberg, we built a non-trivial (roughly 20k loc) DSL -> C++ "transpiler" in OCaml that is in the critical path responsible for building core parts of the infrastructure.

Conflict resolution is not very sofisticated. You can choose to always take server side version (the default) or client side version (see https://github.com/astrada/google-drive-ocamlfuse/wiki/Confi...). My main use case is a single user working on the client or on the server. So the scenario is not of a collaborative app.

works fine with Vim