Reason: A new interface to OCaml • Hacker News Board

Re: Reason: A new interface to OCaml

#41

Post by partiallypro » Tue, May 17, 2016, 9:12 PM UTC

Does anyone Else's Firefox absolutely slow to a crawl on this page?

Edit: just doesn't load at all on Edge. Does load in Chrome/Opera and surprisingly IE 12 but doesn't load the logo's font.

Re: Reason: A new interface to OCaml

#42

Post by ulber » Tue, May 17, 2016, 9:12 PM UTC

This page is completely unusable due to lag. From the other comments it seems this is FF specific. One would think FB would have the resources to test new pages at least on common browsers before publishing.

Edit: The fix came quickly though.

Re: Reason: A new interface to OCaml

#43

Post by andrew_wc_brown » Tue, May 17, 2016, 9:14 PM UTC

Everything reads like double talk. Not sure what I would want to use this for.

Re: Reason: A new interface to OCaml

#44

Post by Polarity » Tue, May 17, 2016, 9:14 PM UTC

ulber wrote: post #42

This page is completely unusable due to lag. From the other comments it seems this is FF specific. One would think FB would have the resources to test new pages at least on common browsers before publishing. Edit: The fix came quickly though.

yea, open page, lag, close page. kthxbye

Re: Reason: A new interface to OCaml

#45

Post by Matthias247 » Tue, May 17, 2016, 9:15 PM UTC

hellodevnull wrote: post #4

Site doesn't load in Firefox. Works in Chrome.

Here too, completley killed Firefox (FF46 on Win10) with an unresponsive browser window.

Re: Reason: A new interface to OCaml

#46

Post by ClosureChain » Tue, May 17, 2016, 9:16 PM UTC

I wonder if the people at Propellerheads will sue Facebook for using the name of their software https://www.propellerheads.se/reason

Re: Reason: A new interface to OCaml

#47

Post by jordwalke » Tue, May 17, 2016, 9:16 PM UTC

ipsum2 wrote: post #34

Looking at http://facebook.github.io/reason/mlCompared.html it looks like regular OCaml, with a sprinkling of JS syntax.

For now, that's somewhat accurate. If you check out the JS comparison page, you might say it looks like JS with OCaml's influence.

The point of the syntax toolchain is actually not to get it right on the first try but to make something viable that is easier to learn/read, avoid bike-shedding, and put all the right tooling in place so that we can very seamlessly upgrade after taking in feedback. It's pretty liberating to know you have that ability to move forward rapidly and automate all of the upgrades.

Re: Reason: A new interface to OCaml

#48

Post by Cyph0n » Tue, May 17, 2016, 9:17 PM UTC

This looks very interesting. I've always had OCaml in mind but never actually got around to using it in a project. Facebook could have done a better job describing what exactly this is, but they do provide a good overview at the end of the page (strangely!) [1].

In summary, Reason [2] is a new language (correction: interface to OCaml) that shares a part of the OCaml compiler toolchain and runtime. I don't know of any language that uses a similar approach, that is, plugging into an existing compiler toolchain. I guess a reasonable yet inaccurate analogy would be Reason -> OCaml is like Elixir -> Erlang or Clojure -> Java.

I hope Reason can provide OCaml with the extra push needed to bring it into the mainstream PL space and more widespread adoption.

[1]: http://facebook.github.io/reason/#how-reason-works

[2]: https://github.com/facebook/reason

Re: Reason: A new interface to OCaml

#49

Post by [deleted] » Tue, May 17, 2016, 9:17 PM UTC

jordwalke wrote: post #28

Paul_S wrote: post #5

Website fries the CPU (FF).

Sounds like FF can't handle gifs, but Chrome/Safari do a good job. I've disabled the gif on the main page just to be friendly to FF while I figure out a better approach. Thanks for the report.

[deleted]

Re: Reason: A new interface to OCaml

#50

Post by animex » Tue, May 17, 2016, 9:17 PM UTC

ulber wrote: post #42

This page is completely unusable due to lag. From the other comments it seems this is FF specific. One would think FB would have the resources to test new pages at least on common browsers before publishing. Edit: The fix came quickly though.

While not cool, that's a pleasant surprise to see something made-first for FF! Glad to see people still fighting against browser mono-culture.

Disclaimer: This post was written in Chrome.