ReScript 8.4(rescript-lang.org)
rescript-lang.org
ReScript 8.4
https://rescript-lang.org/blog/bucklescript-release-8-4
64 comments
This feels a lot like what happened to Hack, which at first was compatible with PHP and could be compiled to it, but later became its own language to better fit FB's needs, and it seems like they're giving OCaml the same treatment here with ReScript.
There was actually some effort being made to keep OCaml tooling compatible with ReasonML (which is supported by dune[0] with no additional configuration) and BuckleScript integration with dune, which was being worked on before this rebrand, so it's kind of sad to see FB going off on their own with ReScript because they don't wanna do the work to upstream the changes they need.
By the way, regular OCaml also has its own JS backend[1] which is of course completely incompatible with BuckleScript.
0: https://dune.build/ 1: https://github.com/ocsigen/js_of_ocaml
There was actually some effort being made to keep OCaml tooling compatible with ReasonML (which is supported by dune[0] with no additional configuration) and BuckleScript integration with dune, which was being worked on before this rebrand, so it's kind of sad to see FB going off on their own with ReScript because they don't wanna do the work to upstream the changes they need.
By the way, regular OCaml also has its own JS backend[1] which is of course completely incompatible with BuckleScript.
0: https://dune.build/ 1: https://github.com/ocsigen/js_of_ocaml
> it's kind of sad to see FB going off on their own with ReScript
ReScript is not a Facebook project. The compiler is licensed by Bloomberg LLP: https://github.com/rescript-lang/rescript-compiler/blob/60a1...
And the syntax is licensed by the ReScript team: https://github.com/rescript-lang/syntax/blob/72d9b7034fc28f3...
The ReScript team is comprised of both Facebook and folks outside Facebook.
ReScript is not a Facebook project. The compiler is licensed by Bloomberg LLP: https://github.com/rescript-lang/rescript-compiler/blob/60a1...
And the syntax is licensed by the ReScript team: https://github.com/rescript-lang/syntax/blob/72d9b7034fc28f3...
The ReScript team is comprised of both Facebook and folks outside Facebook.
not sure if it's FB's decision or the project maintainer's.
I am rather disappointed and think F# 's Fable is a better alternative.
I am rather disappointed and think F# 's Fable is a better alternative.
Sorry to say, it's not. F# is nowhere near the wonderful type-sytem of Ocaml(although it's intentional). I would stick with js_of_ocaml for my js needs.
last time I check, did not find a way to integrate jsoo easily with existing js code. is it any tutorial on how to write a js lib using jsoo?
You have to write binding glue code. Last i saw reason also required binding code to work.
Here is a react binding for jsoo: https://github.com/jchavarri/jsoo-react .
Here is a react binding for jsoo: https://github.com/jchavarri/jsoo-react .
IMO this isn't about whether ReScript wants to upstream their changes, it's a combination of things:
- Reason+BuckleScript was confusing at best, having two websites and different release schedules.
- Reason's goal is to be a 100% mapped syntax for OCaml. This does not mesh well with the goal of producing readable JS, so ReScript will probably end up as a subset of OCaml features.
- Reason syntax changes apparently caused grief when applied to BuckleScript. This one was never very clear, but regardless now that the syntax is in-house the ReScript team can be more responsive with it.
The problem with this transition is that it was dropped on the community in an unfinished state and BuckleScript was retired completely. The goals of the change are, I think, mostly reasonable.
- Reason+BuckleScript was confusing at best, having two websites and different release schedules.
- Reason's goal is to be a 100% mapped syntax for OCaml. This does not mesh well with the goal of producing readable JS, so ReScript will probably end up as a subset of OCaml features.
- Reason syntax changes apparently caused grief when applied to BuckleScript. This one was never very clear, but regardless now that the syntax is in-house the ReScript team can be more responsive with it.
The problem with this transition is that it was dropped on the community in an unfinished state and BuckleScript was retired completely. The goals of the change are, I think, mostly reasonable.
I have no skin in the game w.r.t to OCaml/Reason/etc. I do wish compile-to-JS languages would give up on the readable Javascript thing. I think ClojureScript nailed it with their reliance on Google Closure's aggressive optimization mode __because__ it produces obfuscated, highly optimized output.
Purescript also shares this goal, and it is a bummer, performance-wise, in older browsers that don't handle currying and various other "readable" representations well.
Worse still, if your target output is readable, then someone might start touching the compiled runtime objects with Javascript and then... god help you as you watch the guarantees of your fancy type system unravel before your very eyes.
Purescript also shares this goal, and it is a bummer, performance-wise, in older browsers that don't handle currying and various other "readable" representations well.
Worse still, if your target output is readable, then someone might start touching the compiled runtime objects with Javascript and then... god help you as you watch the guarantees of your fancy type system unravel before your very eyes.
"readable output" isn't really about being human-readable, except in unrealistic example cases. The bigger benefit is shared data types; this helps immensely with JS interop.
https://rescript-lang.org/docs/manual/latest/shared-data-typ...
https://rescript-lang.org/docs/manual/latest/shared-data-typ...
I feel like the dev team is using "readable output" to mean both "human-readable" and "shared data types" depending on the situation. And it creates a lot of confusion.
Spyder81 is partly right, 'readable' doesn't mean 'human-readable' per se, it means rather that the compiler tries very hard to produce output JS that looks like idiomatic, hand-written JS. This means things like:
- Uncurrying functions
- Compiling OCaml modules to idiomatic JavaScript objects
- Compiling OCaml record values to idiomatic JavaScript objects
- Compiling tail recursion to idiomatic while loops
- And so on.
> someone might start touching the compiled runtime objects with Javascript and then... god help you as you watch the guarantees of your fancy type system unravel before your very eyes.
That's exactly what genType is for--it produces JavaScript, TypeScript, and Flow interfaces for ReScript output code so that people in the JS world can consume it transparently.
- Uncurrying functions
- Compiling OCaml modules to idiomatic JavaScript objects
- Compiling OCaml record values to idiomatic JavaScript objects
- Compiling tail recursion to idiomatic while loops
- And so on.
> someone might start touching the compiled runtime objects with Javascript and then... god help you as you watch the guarantees of your fancy type system unravel before your very eyes.
That's exactly what genType is for--it produces JavaScript, TypeScript, and Flow interfaces for ReScript output code so that people in the JS world can consume it transparently.
I'm rather confused: what is ReasonML ? is ReasonML now ReScript, or is it still its own thing? A quick google suggests ReasonML is for targeting native platforms? But I used it for the web at one point?
Anyway, there was already a problem with like three different standard libraries (which had super annoying differences like swapping parameter orders, presumably in an attempt to be friendlier etc.) or something when I first messed around with ReasonML (Bucklescript? Whatever the Facebook one was in 2019? I dunno.) and I hope this isn't also increasing that problem ?
Anyway, there was already a problem with like three different standard libraries (which had super annoying differences like swapping parameter orders, presumably in an attempt to be friendlier etc.) or something when I first messed around with ReasonML (Bucklescript? Whatever the Facebook one was in 2019? I dunno.) and I hope this isn't also increasing that problem ?
ReasonML is merely an "alternate syntax" to OCaml, meaning it's a separate language that parses to the same AST. Traditionally it's been used along with Bucklescript, an OCaml-to-Javascript compiler developed by the same people, to do web work, but it's well-supported in the native OCaml compiler ecosystem as well.
Now that ReScript has superseded ReasonML+Bucklescript, the only niche remaining for non-legacy ReasonML is native development work by folks who just don't like the normal OCaml syntax, or want to target both runtimes with the same code.
Basically, the permutations are like this, with "ReScript (backend)" referring to the thing formerly known as BuckleScript:
OCaml/native: What normal people think of when they hear "OCaml".
ReasonML/native: Uncommon, but supported for folks who've bought into the Reason syntax.
ReScript (frontend)/native: Nobody does this since ReScript is strictly worse than ReasonML when targeting native. I don't even know if it's possible.
OCaml/ReScript (backend): Should be possible, but nobody does this.
ReasonML/ReScript (backend): Sort-of-deprecated in favor of the new syntax, but still supported, and most pre-existing projects are probably still using this.
ReScript (frontend)/ReScript (backend): Now collectively known as "ReScript" and the focus of the team going forward. New web projects are expected to use this.
Now that ReScript has superseded ReasonML+Bucklescript, the only niche remaining for non-legacy ReasonML is native development work by folks who just don't like the normal OCaml syntax, or want to target both runtimes with the same code.
Basically, the permutations are like this, with "ReScript (backend)" referring to the thing formerly known as BuckleScript:
OCaml/native: What normal people think of when they hear "OCaml".
ReasonML/native: Uncommon, but supported for folks who've bought into the Reason syntax.
ReScript (frontend)/native: Nobody does this since ReScript is strictly worse than ReasonML when targeting native. I don't even know if it's possible.
OCaml/ReScript (backend): Should be possible, but nobody does this.
ReasonML/ReScript (backend): Sort-of-deprecated in favor of the new syntax, but still supported, and most pre-existing projects are probably still using this.
ReScript (frontend)/ReScript (backend): Now collectively known as "ReScript" and the focus of the team going forward. New web projects are expected to use this.
Thanks. That makes it very clear (to me), although definitely a harder sell to have to explain all these possibilities to others.
AFAIK there isn't a ReScript to Native compiler. The way to do server-side ReScript is to use Node.
Paul Biggar of Darklang started a stdlibrary called tablecloth which offers the same API on frontend (Bucklescript/Reason) and backend (OCaml).
Yet he too gave up on ocaml
Yet another standard library for OCaml? You sure it wasn't a parody? :)
I can think of: TheActualStdlib, Base/Core_kernel/Core, Batteries, Containers, Belt, ...
I can think of: TheActualStdlib, Base/Core_kernel/Core, Batteries, Containers, Belt, ...
It has different goals from them: https://github.com/darklang/tablecloth
Feeling the same about this. Things were far clearer prior to this year -- I can no longer really see the point of the project and I'm just a bit sad about how it's all evolved. I've been following it since just before FB came in with ReasonML. I'd just started playing around with OCaml, found Bucklescript (which I still think is a marvel). Reason seemed like a way [albeit via that syntax] to get some traction for a very good language that imo seriously lacks in community, libraries and documentation. It felt slightly like Elixir, filling in a few holes in the underlying language and adding a layer of consistency. And it seeed a very good alternative to TS. But instead of coalescing into something, it seems to have just fragmented things further
I hope something good does coalesce, but it's currently very confusing. Maybe just me but the opportunity feels like it's slipping away. As say, been following things very closely so I fully appreciate some the issues & understand some hidden things are based on internal needs of that part of FB
I hope something good does coalesce, but it's currently very confusing. Maybe just me but the opportunity feels like it's slipping away. As say, been following things very closely so I fully appreciate some the issues & understand some hidden things are based on internal needs of that part of FB
Moreover it's hard to figure out which Ocaml version is Rescript on? Last i checked it was on 4.06, Do they backport any features, bugfixes?
Now it seems like it's a complete fork with a new syntax. Maybe it serves the interest of people at facebook, but Ocaml users are unlikely to be using this instead of js_of_ocaml.
Now it seems like it's a complete fork with a new syntax. Maybe it serves the interest of people at facebook, but Ocaml users are unlikely to be using this instead of js_of_ocaml.
well. rescript still compile pure ocaml code just fine.
I think the only cool project using ReasonML that is native is revery[0], which is being used for onivim[1].
[0]: https://github.com/revery-ui/revery [1]: https://onivim.io/
[0]: https://github.com/revery-ui/revery [1]: https://onivim.io/
I am very disappointed by this as well. I am worried ReScript may have killed the momentum ReasonML had been gaining.
This is how I understand this:
What was the goal? If it was to ease adoption by newcomers, as a newcomer, it has made this more difficult. As someone VERY EAGER to enter this family of languages today, I ended up giving up on all of that and decided to just learn OCaml.
Now I'm dealing with Dune, Esy, OPAM, two competing async libraries and a community that is split between Jane Street libraries and the others.. but I really, really like OCaml!
This is how I understand this:
1996 - OCaml is born.
2016 - ReasonML, an alternative syntax that compiles to OCaml, is launched by Facebook.
2016 - A couple of months later, BuckleScript, an OCaml -> JS compiler is launched.
201X - Collaboration happens, BuckleScript couples tightly to ReasonML.
2020 - BuckleScript forks the ReasonML syntax and rebrands the compiler and the new syntax together under ReScript.
2020 - ReasonML still exists?
What was the goal? If it was to ease adoption by newcomers, as a newcomer, it has made this more difficult. As someone VERY EAGER to enter this family of languages today, I ended up giving up on all of that and decided to just learn OCaml.
Now I'm dealing with Dune, Esy, OPAM, two competing async libraries and a community that is split between Jane Street libraries and the others.. but I really, really like OCaml!
> If it was to ease adoption by newcomers, as a newcomer, it has made this more difficult. As someone VERY EAGER to enter this family of languages today, I ended up giving up on all of that and decided to just learn OCaml.
This was my exact path. A friend and I wanted to make a small SaaS using Reason for the backend, because it smoothed out a bunch of what we considered were "rough edges" in OCaml. Then the ReScript split happened, and we realised that Reason was dead for all intents and purposes. It's hard to imagine the Reason team will continue updating Reason when they're focusing hard on ReScript instead.
This was my exact path. A friend and I wanted to make a small SaaS using Reason for the backend, because it smoothed out a bunch of what we considered were "rough edges" in OCaml. Then the ReScript split happened, and we realised that Reason was dead for all intents and purposes. It's hard to imagine the Reason team will continue updating Reason when they're focusing hard on ReScript instead.
here's the thing, _I don't think ReasonML is dead_! I've tried to dig for more clarity in the GitHub issue trackers and come up with mostly nothing. I am starting to get the feeling there is some kind of dispute or falling out between the maintainers of the two projects.
ReasonML isn't dead, but the way I heard the story it has always been a spare time project not a properly funded FB team. There was just enough spare time early on to get the community excited.
From the same source, I heard ReScript does have funding behind it.
From the same source, I heard ReScript does have funding behind it.
For me, being an old dog, it is quite clear. Yet another guest language that fades away.
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?
I feel like this fork might make sense inside Bloomberg, but it’s killed my enthusiasm for this language family.
I feel like this fork might make sense inside Bloomberg, but it’s killed my enthusiasm for this language family.
[deleted]
Theoretically, ReScript will support ReasonML syntax, and theoretically ReasonML can still be used for native development.
The messaging isn't clear on ReasonML's future at ALL though. Is it essentially deprecated until the full switch to ReScript happens? The Rescript FAQ mentions changes will be additive in supporting ReasonML, and they will track new features to OCaml, but will they track new features to Reason? Will anyone actively develop Reason anymore?
The messaging isn't clear on ReasonML's future at ALL though. Is it essentially deprecated until the full switch to ReScript happens? The Rescript FAQ mentions changes will be additive in supporting ReasonML, and they will track new features to OCaml, but will they track new features to Reason? Will anyone actively develop Reason anymore?
ReasonML is, as it has always been, a 100% syntax map to OCaml. It will always be that, but moving forward it will be nothing more than that. Compiling future ReasonML versions to JS will require js_of_ocaml.
The success of BuckleScript meant that a _lot_ of people used what they thought was ReasonML but it was really ReasonML+BuckleScript. This lead to a ton of confusion the moment newcomers realised they needed a second website to look up APIs.
ReScript includes a snapshot version of ReasonML for backwards compatibility, but it will never be upgraded.
The future of ReasonML is likely slow and steady progress, potentially fading into obscurity as the target audience is now very small (OCaml developers who don't like OCaml syntax).
The success of BuckleScript meant that a _lot_ of people used what they thought was ReasonML but it was really ReasonML+BuckleScript. This lead to a ton of confusion the moment newcomers realised they needed a second website to look up APIs.
ReScript includes a snapshot version of ReasonML for backwards compatibility, but it will never be upgraded.
The future of ReasonML is likely slow and steady progress, potentially fading into obscurity as the target audience is now very small (OCaml developers who don't like OCaml syntax).
You might have been able to use the same syntax before, but writing code for Reason native was already very different to writing Reason+BuckleScript for the browser. This just formalises the split.
To write the same code for both front and back end js_of_ocaml has been the standard since long before Reason came along, and it works just fine with Reason native.
To write the same code for both front and back end js_of_ocaml has been the standard since long before Reason came along, and it works just fine with Reason native.
actually bucklescript has never really been used at bloomberg. And bob left bloomberg a long time ago. So this fork is definitely not happening because of bloomberg.
To have code that you can compile to both native and js, the easiest thing is to stick to the ocaml syntax. It is supported by all the versions of the compiler (rescript or ocaml). And to also use the ocaml syntax for the tools doing code generation, such as atdgen.
To have code that you can compile to both native and js, the easiest thing is to stick to the ocaml syntax. It is supported by all the versions of the compiler (rescript or ocaml). And to also use the ocaml syntax for the tools doing code generation, such as atdgen.
That's very doable, but tedious to make and it's probably on of the selling points for Reason. Writting React code with OCaml is very tedious.
Are there any good examples of open source projects written with ReScript?
I was searching for this recently and came up short... Is it mainly being used inside Facebook?
Kind of a shame as the ideas look good. I would like something like Elm, but Elm doesn't interoperate with JS.
I was searching for this recently and came up short... Is it mainly being used inside Facebook?
Kind of a shame as the ideas look good. I would like something like Elm, but Elm doesn't interoperate with JS.
> I would like something like Elm, but Elm doesn't interoperate with JS.
You can try Mint: https://www.mint-lang.com
I've created it because I wanted something like Elm but with easier JS interop and less boilerplate :)
You can try Mint: https://www.mint-lang.com
I've created it because I wanted something like Elm but with easier JS interop and less boilerplate :)
This looks very cool. Do you have a roadmap?
> This looks very cool.
Thanks :)
> Do you have a roadmap?
It's no written roadmap yet, currently I'm working on a UI library which is written in Mint, and these are things which the majority of people want which I'll work on next:
- Language Server
- Server Side Rendering
- Interfacing with NPM libraries
- Some new language features and cleanup of some of the existing ones
- A proper Time module
After those I think we can release 1.0 and focus on bugfixes and optimizations.
Thanks :)
> Do you have a roadmap?
It's no written roadmap yet, currently I'm working on a UI library which is written in Mint, and these are things which the majority of people want which I'll work on next:
- Language Server
- Server Side Rendering
- Interfacing with NPM libraries
- Some new language features and cleanup of some of the existing ones
- A proper Time module
After those I think we can release 1.0 and focus on bugfixes and optimizations.
Thanks! Language server sounds particularly exciting. I'll be watching this project eagerly.
You should give F# a try. Check out Feliz [0], it integrates flawlessly with React and you can use elmish for the internal state management of components. You can use F# on the backend as well (Giraffe, Saturn) and use Fable.Remoting for RPC.
[0] https://github.com/Zaid-Ajaj/Feliz [1] https://github.com/Zaid-Ajaj/Fable.Remoting
[0] https://github.com/Zaid-Ajaj/Feliz [1] https://github.com/Zaid-Ajaj/Fable.Remoting
Fable (F#) has interop with JS and examples using an Elm architecture.
The TinyMCE team is building a big new feature with it
https://www.tiny.cloud/blog/tinymce-reasonml/
We aren't sure when we will be able to open source the new model, and we are still using Reason syntax with the ReScript compiler, but we will transition to ReScript syntax eventually.
https://www.tiny.cloud/blog/tinymce-reasonml/
We aren't sure when we will be able to open source the new model, and we are still using Reason syntax with the ReScript compiler, but we will transition to ReScript syntax eventually.
actually I think that it is basically not used inside facebook anymore. But it is used in a bunch of other companies.
...who are you? Everything you said in this subthread is false, and you seem to have a weird chip on your shoulder regarding this.
well sorry if this isn't true, but I haven't insulted anyone. If I get those feedback and they are incorrect, I hope that you can provide my insightful ones to clear the situation.
I've replied earlier with concrete details in another place in this subthread. You indeed haven't insulted anyone, but your comment history does indicate some biased intent; if the ecosystem changes affected you, we'd like to apologize for those; let's bury the hatchet here because maybe we can both agree that drama isn't productive.
I don’t see how there’s a biased intent. I’ve no shares in any tech. If anything I wish for rescript to be a big success given how much the company I am in relies on it. I’ve contributed to multiple bucklescript projects. And I’m not criticising the decisions of anyone.
Hm so what does Facebook use? I saw a talk that was marketing Reason as "React as a language"?
Is that true for ReScript, or no?
Presumably Facebook still uses React? But they use it via regular JS and not Reason or Rescript?
I do have to concur with some of the comments -- the situation seems pretty confusing, and spending a bunch of time looking at docs didn't enlighten me.
Is that true for ReScript, or no?
Presumably Facebook still uses React? But they use it via regular JS and not Reason or Rescript?
I do have to concur with some of the comments -- the situation seems pretty confusing, and spending a bunch of time looking at docs didn't enlighten me.
from what I heard, they use typescript instead of reason for some time already. I don't know if they use react or not. I also heard that they weren't always using reasonreact even when they were using reason. So they've never been 100% on the same stack than what was advertised by the reason team.
It probably explain why fb dedicates so little resources to reason too.
It probably explain why fb dedicates so little resources to reason too.
We did use Reason and ReasonReact. Not sure where you're getting your info. And no we don't use TypeScript on the team...
Btw for people who want to use js_of_ocaml instead of rescript but still like react, there is https://github.com/jchavarri/jsoo-react. It's obviously not as polished. But it's interesting to see how much work it requires to bind a large lib like react.
That's a project that we all wished was in a perfect shape in order to make Reason more approchable with jsoo.
https://github.com/facebook/reason/issues/2634
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!
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.
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.
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.
Just realized that https://reasonml.org is deprecated.
It was never official, and the people behind it folded into the new ReScript team.
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.
So now as of 12/14/2020 there are three Ocaml syntax versions in use:
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)
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.