Reasons that people were forced to move from Elm to something else?

[rupert]

@solificati

The problem with Elm not being 1.0 or more is that by convention we should expect more breaking changes out of nowhere. This is a signal that Elm is in design phase and core team is focused on creating Elm as perfect language and not maintaining it as developers tool.

I think this is true, its a petty thing but the number does matter. Elm should bump to 1.0.0 or perhaps 19.1 in my view.

It was announced here that Elm is unlikely to change in any significant way for maybe 2 or 3 years:

Where can we find the roadmap of Elm?

If you like what you see now, that’s pretty much what Elm is going to be for a while. I’m currently doing some exploratory work. It is still too early to tell which parts of that might work out, so there is no real news to share at this point. If this works out, even in the wildest version of success, I wouldn’t expect the language or core packages to change very much. Maybe two or three years down the line it could reveal something that’d be good to fix up, but I don’t really foresee notable …

Which is awesome from a quality and stability perspective. Not so good if you are hanging on for a bug fix.

To give an example, we created a PR for a stack overflow problem in the time-travel debugger. Should take 10 minutes to review and merge in, its just the minimal set of changes needed to make a certain function tail recursive. When your PR doesn’t get merged in, you don’t bother to make the next one.