# Tail-call optimization in Elm **URL:** \ **Category:** Blogs/Articles/Talks/Podcasts\ **Tags:** elm\ **Created:** [12 June 2021 03:12 UTC](https://forum.devtalk.com/t/tail-call-optimization-in-elm/10459 "2021-06-12T03:12:40Z")\ **Posts on this page:** 1\ **Showing post:** 11
**Author:** ![OvermindDL1](https://forum.devtalk.com/user_avatar/forum.devtalk.com/overminddl1/32/52_2.png) [@OvermindDL1](https://forum.devtalk.com/u/OvermindDL1)\ **Post date:** [24 June 2021 22:54 UTC](https://forum.devtalk.com/t/tail-call-optimization-in-elm/10459/11 "2021-06-24T22:54:27Z")
> [@rustkas](#): > > [ReasonML](https://reasonml.github.io/en/) has not yet looked (a quick glance at the description - I see positive reviews. Implemented on the basis of [OCalm](https://ocaml.org/)). ReasonML is just a PP (preprocessor) for OCaml. You can generate normal OCaml programs with it, or plug in other OCaml backends, like say JSOO or [bucklescript](https://forum.devtalk.com/t/on-ocaml-and-the-js-platform/7898) (or whatever its called now) to generate javascript for example. ReasonML comes with a very node-centric array of ecosystem tools to fit in to that all though, quite easy to pick up. > [@rustkas](#): > > He has a [large community](https://discourse.elm-lang.org/), too That community has a lot of churn though. In general there’s a small set of dedicated people who stick around, but a few select some of them are rather hostile to new users, which tends to drive them away. As for the language, it has a lot of design issues, many of which have repeatedly caused miscompilations over time, and that’s even before getting to the elm architecture style of doing things (which is just a standard centralized event processor), which is overall fine, but rather difficult to work with, especially when combining with other things for a variety of reasons. I tried to use it in earnest for over a year, but a combination of language misdesigns and the hostile community were, not pleasant… \>.\> Even things like the OP article just outright lying (there is no TCO in elm) has been a common pattern over time. --- _[View the full topic](https://forum.devtalk.com/t/tail-call-optimization-in-elm/10459)._