Js_of_ocaml takes lowlevel bytecode from OCaml compiler, BuckleScript takes the highlevel rawlambda representation from OCaml compiler
Js_of_ocaml focuses more on existing OCaml eco-system(opam) while BuckleScript's major goal is to target npm
Js_of_ocaml and BuckleScript have slightly different runtime encoding in several places, for example, BuckleScript encodes OCaml Array as JS Array while js_of_ocaml requires its index 0 to be of value 0.
Both projects are improving quickly, so this can change in the future!
I don't claim to be knowledgeable with OCaml, but I use it on and off since a couple of years and wrote about my thoughts when it was first released[0]. tl;dr: don't like the syntax, for the most part it's worse than OCaml itself. The rest is alright and helps the OCaml ecosystem as well, the focus on better tooling is good.
I know it's dumb that the thing holding me back from OCaml is the syntax, but after giving up on an Om project I've come to accept js will always be the greatest common denominator.
As I recall, Reason is the current project of React originator Jordan Walke and React contributor Cheng Lou. I wouldn't be at all surprised to see a Facebook project emerge that allows you to author React apps in Reason with Bucklescript.
Js_of_ocaml takes lowlevel bytecode from OCaml compiler, BuckleScript takes the highlevel rawlambda representation from OCaml compiler
Js_of_ocaml focuses more on existing OCaml eco-system(opam) while BuckleScript's major goal is to target npm
Js_of_ocaml and BuckleScript have slightly different runtime encoding in several places, for example, BuckleScript encodes OCaml Array as JS Array while js_of_ocaml requires its index 0 to be of value 0.
Both projects are improving quickly, so this can change in the future!