Live data from Hacker News

Compile OCaml to JavaScript, use ReactJS, bindings to ReactJS, several examples

github.com

11–20 of 31 posts

Re: Compile OCaml to JavaScript, use ReactJS, bindings to ReactJS, several examples

#11

Earlier quoted context omitted.

I haven't really gotten into much ML yet, and I'm curious to hear what people knowledgeable with OCaml think about http://facebook.github.io/reason/ The name makes it impossible to research to find any blog posts or anything, but the familiar syntax alone might make it at least a first step for me.

Speaking for myself, I think Reason is a very good thing and rewriting this in Reason or adding a Reason layer is a goal/TODO.

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.

Re: Compile OCaml to JavaScript, use ReactJS, bindings to ReactJS, several examples

#12

Earlier quoted context omitted.

Speaking for myself, I think Reason is a very good thing and rewriting this in Reason or adding a Reason layer is a goal/TODO.

That's awesome and great work. 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.

I don't blame you, ES6 can be stupid concise and enjoyable. I practice most of my algorithms prep coding in it.

Re: Compile OCaml to JavaScript, use ReactJS, bindings to ReactJS, several examples

#15

In the same vein, there are also some F# to JS compiler projects such as Funscript ( http://funscript.info/ ) and Fable ( https://github.com/fsprojects/Fable ). F# is an open-source Ocaml inspired language for .net.

Also plugging Websharper (http://websharper.com/) which is a full web framework that includes a F# to JS compiler to write the client-side part of the code.

Though you can use just the compiler inside a regular ASP.NET MVC project, if you so choose.

Re: Compile OCaml to JavaScript, use ReactJS, bindings to ReactJS, several examples

#16
post #7

Earlier quoted context omitted.

Differences from js_of_ocaml (not an easy find) 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…

I haven't really gotten into much ML yet, and I'm curious to hear what people knowledgeable with OCaml think about http://facebook.github.io/reason/ The name makes it impossible to research to find any blog posts or anything, but the familiar syntax alone might make it at least a first step for me.

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.

[0]: https://xivilization.net/~marek/blog/2016/05/19/reason-lets-...

Re: Compile OCaml to JavaScript, use ReactJS, bindings to ReactJS, several examples

#17

Why?

A sane, powerful type system is actually enough of a rationale and a selling point, at least for me.

Also, allowing side-effects while still providing the mentioned type system makes it potentially much easier to integrate with existing JS code.

Re: Compile OCaml to JavaScript, use ReactJS, bindings to ReactJS, several examples

#18

Why?

A sane, powerful type system is actually enough of a rationale and a selling point, at least for me. Also, allowing side-effects while still providing the mentioned type system makes it potentially much easier to integrate with existing JS code.

Another reason for it being "much easier to integrate with existing JS code" is strict evaluation.

Haskell is lazy, which means using GHCJS to compile it to JS produces code full of explicit thunks (think of promises). Both Elm and PureScript are compile-to-JS-languages that inherit a lot from Haskell, but not it's laziness.

Re: Compile OCaml to JavaScript, use ReactJS, bindings to ReactJS, several examples

#19
post #5

For those interested in this, https://github.com/bloomberg/bucklescript is an alternate (albeit new) OCaml to JS compiler. There's already talk about supporting JSX syntax: https://github.com/bloomberg/bucklescript/issues/162

Sander sent a [Pull Request](https://github.com/facebook/reason/pull/647) to [Reason](http://facebook.github.io/reason/) which adds JSX syntax (which many React developers have found helpful)

Reason doesn't yet work with Edgar(OP)'s React bindings yet, but it could easily (and therefore JSX would work as well).

Re: Compile OCaml to JavaScript, use ReactJS, bindings to ReactJS, several examples

#20

Earlier quoted context omitted.

Speaking for myself, I think Reason is a very good thing and rewriting this in Reason or adding a Reason layer is a goal/TODO.

That's awesome and great work. 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.

Maybe consider Scala? It's an ML family language with more familiar syntax, and also has a Javascript backend.
Post reply on HN