The FAQ says "you temporarily grant us access to your public repositories", so I'm thinking this probably means your Github repos become writable to an attacker.
New readers might want to check out the FAQ before diving in .
EDIT: Some more info from the email.
"Release notes for beta1:
- The first-class modules chapter is incomplete, pending some portability
improvements to the ocaml-plugins Core library.
- The binary serialization chapter is also incomplete, but has just enough
to teach you about the Async RPC library.
- The installation chapter will be revised in anticipation of the OCaml 4.1
release, and is currently quite source-based.
- The packaging and build systems chapter hasn't been started yet. We're
still deciding whether or not to make this an online pointer rather than
a print chapter, since it's likely to change quite fast.
- We are preparing exercises per chapter that are not included in this
particular beta release, but will be available online as soon as possible.
- The code examples will all be clonable as a separate repository in beta2."
"We just want the ability to create issues in one specific public repository, but the minimum privileges we can request from Github are the ones you see when you login."
OCaml global lock on the INRIA implementation might eventually be fixed.
Both are pretty good alternatives to Go if you are more into FP and modern language abstractions.
* multiple processes (there are a few libraries that can help make it easier)
* I/O concurrency with cooperative threads library: Equeue, Lwt or Async
* you could also use the built-in Thread module for I/O concurrency but the overhead will likely be higher
* you can execute C code in multiple threads in parallel, only OCaml code is limited to a single thread (due to the global lock)
I could google but I'm fishing for your recommendations as well.
(edit to address questions/comments)
I haven't actually used it so I have no idea if it's ready for "real" use (whatever that means! everyone has a different definition) However, it's under active development which is more than you can say for ML. I only found it when I saw the above comment and thought "I wonder if there is an ML for the JVM" but I have put it on my own todo list to check it out.
And I know the pain of which you speak pjmlp, I have to use PHP for my day job...
Fortune 500 enterprise development, offshoring and modern programming languages are hard to combine.
I love scala, but I do find myself wishing method names were required to be alphanumeric.
I've not looked at typed channels at all, but yeah, thats annoying.
Scalaz and Shapeless are designed to do crazy type level stuff, taking their inspiration from type/group/set theory.
And yes, I agree Scala is the successor to Perl (but I have no problem with that :p )
The app Real World OCaml Commenting will be able to:
Read your public information.
Update your public repositories (Commits, Issues, etc).
However, we never store your authorization tokens in our server, and instead just directly pass your authorization token into a client-side cookie.
has become rather dated.
But you will still need the reference manual and some other sources as it seems rather sketchy in some aspects (syntax extensions, C bindings)
(I've made lots of small comments in the book, hoping it may help)
In this era of Scala, Clojure, F#, (and Erlang), what use cases of OCaml would interest developers to dive into it?