DEV Community

loading...

Discussion on: ReasonML for production React Apps? 🤔 (Part 3)

Collapse
theodesp profile image
Theofanis Despoudis

Lack of documentation is a ship stopper. Thats why Reason is a no-go area for now.

Collapse
hagnerd profile image
Matt Hagner

The lack of documentation surrounding Reason, Reason React, and the whole Reason / OCaml ecosystem is definitely a bummer.

It's no substitution, but Reason and OCaml code both tend to be extremely self documenting if you dive into the source code, due to the strong typing and interface files.

I'm hoping that this is an issue that can start to be solved because Reason and OCaml are both great, but without proper documentation it will be struggle to get people to adopt them in their projects.

Collapse
theodesp profile image
Theofanis Despoudis

It's also the fact that there as so few threads in Stackoverflow and Reddit. I don't even see people writing about it. Just sporadically.

Collapse
seif_ghezala profile image
Seif Ghezala 🇩🇿 Author

I feel you, there are definitely certain gaps in the documentation. I think it's still very good documentation though. I can say that because I managed to write this series just by reading Reason & ReasonReact documentation. During the few times where I got stuck, the community on the forums & Discord was immediately helpful.