The idea that this document counts as a "elm roadmap" explains all you need to know about the future of elm. On any elm discussion board, you'll find people cl

The idea that this document counts as a "elm roadmap" explains all you need to know about the future of elm. On any elm discussion board, you'll find people clamoring for updates, trying to tease out what the language's founder is up to... and this is the result of that, a document that can be summarized as "I'm experimenting with some stuff, stay tuned." Is it any wonder that this leads to anxiety among would-be adopters? Elm's pluses are: * elegant language, and fairly fast * it's got an active community on discord * it's got a huge stable of packages (https://korban.net/elm/catalog/) Is that enough for pet projects? Yes, and there are plenty of people hacking and having fun and being productive. But there are serious questions for anything besides pet projects: Where is the language going? Who is stewarding it, and what are their goals? Why must all packages restricted to package.elm-lang.org (https://lukeplant.me.uk/blog/posts/why-im-leaving-elm/#technical-limitations https://lukeplant.me.uk/blog/posts/why-im-leaving-elm/#techn...)? Why do first-party elm packages get to use an escape hatch to javascript, but other packages cannot (https://lukeplant.me.uk/blog/posts/why-im-leaving-elm/#fairness https://lukeplant.me.uk/blog/posts/why-im-leaving-elm/#fairn...)? These have been brought up here before https://news.ycombinator.com/item?id=22821447 https://news.ycombinator.com/item?id=22821447