My impression of Elm was that it&#x27;s trying to create a platform for real-time interaction (e.g. games, UIs, etc.) that happens to target the browser. There&#x27;s a constant undercurrent of practicality in the community: for example, new language features are regarded suspiciously, and modifications to existing behaviour are only made when they reduce the burden of complexity to the programmer. Obviously it&#x27;s a language that has yet to hit 1.0 so there are occasionally large swings in its design, but apparently they&#x27;ve become more stable as of late (I&#x27;m only picked it up ~1 month ago).<p>The only unpractical part I&#x27;d noticed was its perspective on reusing components, as seen in this overview under &#x27;Nesting&#x27; [1]. That bit of explicit routing aside, may I ask what dissuaded you from using the language seriously?<p>[1]: <a href="https:&#x2F;&#x2F;gist.github.com&#x2F;evancz&#x2F;2b2ba366cae1887fe621#nesting" rel="nofollow">https:&#x2F;&#x2F;gist.github.com&#x2F;evancz&#x2F;2b2ba366cae1887fe621#nesting</a>