# Request: Elm 0.19.2: any update to help adoption to prove that Elm is not dead?

**URL:** <https://discourse.elm-lang.org/t/request-elm-0-19-2-any-update-to-help-adoption-to-prove-that-elm-is-not-dead/8843>\
**Category:** Request Feedback\
**Created:** [December 22, 2022, 6:22pm UTC](https://discourse.elm-lang.org/t/request-elm-0-19-2-any-update-to-help-adoption-to-prove-that-elm-is-not-dead/8843 "2022-12-22T18:22:58Z")\
**Posts on this page:** 1\
**Showing post:** 78

<div class="post-metadata">

**Author:** ![rupert](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.elm-lang.org/rupert/32/1775_2.png) [@rupert](https://discourse.elm-lang.org/u/rupert)\
**Post date:** [February 9, 2023, 2:23pm UTC](https://discourse.elm-lang.org/t/request-elm-0-19-2-any-update-to-help-adoption-to-prove-that-elm-is-not-dead/8843/78 "2023-02-09T14:23:16Z")

</div>

> [@Magnetize2072](#):
>
> Sounds like you should create a thread with a formal proposal, see how many others would be willing to commit to a legit community fork.

Ta da!

> [@Core library fixes and improvements: Part 2](https://discourse.elm-lang.org/t/core-library-fixes-and-improvements-part-2/8055):
>
> So I said I would do some analysis on bugs on the compiler and core packages in order to help inform disucssion around how we can move forward with this. I was thinking I would have time over the xmas holidays, turns out I had even less free time then vs when I am working! Anyway, I now have a spreadsheet organized in a way that enables me to communicate my findings: Pull Requests I analysed anything people asked me to, plus all the outstanding PRs on core packages and the compiler. It made s…

Similar to my theme on the just previous post. Internet/information overload - we are doomed to repeat ourselves in an endless cycle.

---

_[View the full topic](https://discourse.elm-lang.org/t/request-elm-0-19-2-any-update-to-help-adoption-to-prove-that-elm-is-not-dead/8843)._