> 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 :)

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! 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

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.

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.

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.

We did use Reason and ReasonReact. Not sure where you're getting your info. And no we don't use TypeScript on the team...

Not in Messenger too?

from the feedback I got, they migrated to something else