I'm pretty disappointed with the way this has unfolded.<p>For those now familiar with ReScript, ReScript started as "reason" an alternative syntax for Ocaml. Recently ReScript was created with a sytnax more similar to TypeScript than "Reason". In addition, there is a fork of OCaml for compiling to javascript that used to be branded as "Bucklescript", but now it is called "ReScript" as well.<p>So now as of 12/14/2020 there are three Ocaml syntax versions in use:<p>Ocaml,
Reason (Reason 3.6, last version available for native code)
ReScript, (~Reason 4, only available for javascript compiler fork, some sytax present in Ocaml/Reason has actually been removed with no equivilant in the grammar)<p>I am not sure who benefits from this, Ocaml is a serious language that will never be as simple as a dynamically typed language. I am not sure who this is supposed to be helping. It seems to me that things were more clear a year ago when there were just two syntaxes available. In addition, it now takes a relative subject matter expert to disipher what is going on, which i think is the exact outcome ReScript was trying to avoid.
I want to write my front end and back end in the same language - Reason - and compile the backend to native code. So, ReScript doesn’t work for me? Are people still using or working on Reason, or is it dead?<p>I feel like this fork might make sense inside Bloomberg, but it’s killed my enthusiasm for this language family.
Are there any good examples of open source projects written with ReScript?<p>I was searching for this recently and came up short... Is it mainly being used inside Facebook?<p>Kind of a shame as the ideas look good. I would like something like Elm, but Elm doesn't interoperate with JS.
Btw for people who want to use js_of_ocaml instead of rescript but still like react, there is <a href="https://github.com/jchavarri/jsoo-react" rel="nofollow">https://github.com/jchavarri/jsoo-react</a>. It's obviously not as polished. But it's interesting to see how much work it requires to bind a large lib like react.
<a href="https://github.com/facebook/reason/issues/2634" rel="nofollow">https://github.com/facebook/reason/issues/2634</a><p>This issue is trying asking for some explanation regarding the future of ReasonML. Maybe comment/react/subscribe to stay up to date on this issue!
I know Reason/Rescript was to make OCaml's type system available to the JS devs and is an excellent alternative to typescript but its quite hard to follow. I'm a JS developer with no experience in statically typed languages. I'm not able to figure out what exactly is the way to do things we usually do in JS ecosystem. I mean things like a package manager, build system. These things are confusing. I'm pretty sure that there are tons of people turned away from Reason for this very same reason.<p>Also OCaml in Windows was hard to configure and get right. The barrier to entry into the ecosystem is huge and it has to be resolved. The language is beautiful but anyone needs to be able to get productive in it very quickly.