I've read the transcript of the video for the first two questions, "What's The State Of Elm?" and "What’s Evan Working On?". After 12 minutes of chatting, I could still not grasp the beginning of an answer to these questions.
For "What's The State Of Elm?", the developer only explains why there hasn't been a release for 5 years:
- He felt his work wasn't recognized enough by the company he worked for.
- He created a foundation to collect donations, but felt he would not feel at ease with that.
- He has one sentence about the covid: "Okay, and so we did have a pandemic, so maybe that's the fact."
- His work was a long-term investment that did not "meet the needs or the demands of everybody else".
- He talked with many companies that used Elm. But he always got the response "The answer was always like, well, it's going pretty good. We're actually struggling a lot with our backend.".
I think his memory is failing him on this last point. I'd be extremely surprised that companies that used Elm could never find any fault with the language or the compiler. I can remember two essays where companies were glad for Elm, but with serious technical problems, like the inability to host private packages.
I love Elm but I think it's pretty clear that Evan is effectively declaring it as abandonware because he couldn't figure out a business model to sustain him.
What’s Evan Working On?
Sounds like he's talking to a handful of companies that he knows uses Elm and doing some tinkering without any defined objectives.
For "What's The State Of Elm?", the developer only explains why there hasn't been a release for 5 years:
- He felt his work wasn't recognized enough by the company he worked for.
- He created a foundation to collect donations, but felt he would not feel at ease with that.
- He has one sentence about the covid: "Okay, and so we did have a pandemic, so maybe that's the fact."
- His work was a long-term investment that did not "meet the needs or the demands of everybody else".
- He talked with many companies that used Elm. But he always got the response "The answer was always like, well, it's going pretty good. We're actually struggling a lot with our backend.".
I think his memory is failing him on this last point. I'd be extremely surprised that companies that used Elm could never find any fault with the language or the compiler. I can remember two essays where companies were glad for Elm, but with serious technical problems, like the inability to host private packages.