1. 30
  1. 7

    I liked this article, I thought it was well-written, and I learned a few things.

    I was a bit surprised that they didn’t touch on the thing I see that’s most discussed about Elm, which is the state and future of development. Perhaps they thought it was out of scope, or talked about enough elsewhere.

    It’s been 15 months since the last Elm release (0.19.1) and the Github pulse for the repo looks like it’s barely beating (I don’t want to read too much into that). Are there Elm developers here? What’s your take on this?

    1. 3

      There was a thread on that last year, but I do not know how much of that has changed since then:


      1. 2

        Really glad I read that. Thanks!

      2. 3

        Not an Elm developer (used to use it, slowly removing it from our codebase), but I believe Elm development is done significantly in private, so code is only typically visible upon release. Because of this it does look dead between releases.

        I gather the reason for this is something akin to creative control, not wanting to over-promise or set the wrong expectations, things like that. It’s an interesting take on open source culture, and @srid’s comment links to a good rebuttal to it, however I’ve also found hearing it direct from the Elm developers to be a fairly convincing argument at times.

        1. 4

          I can think of some (but very few) other projects successfully following this mode - sqlite comes to mind. I think it requires a very particular sort of core team.

          1. 1

            used to use it, slowly removing it from our codebase

            Thanks for your comment, would you mind elaborating on why you’re slowly removing it? I’ve always thought it looked like a lovely language, but it’s really unclear to me at the moment whether it’s got any future outside of teams that are already committed (on one side there’s Typescript, on the other Purescript and Mint; the latter seems like more-actively-developed Elm-alike language)