On Jul 10, 2016, at 12:40 PM, Mark Hamburg <[email protected]> wrote: > > This also points to a bigger issue with Elm not living up to its "no runtime > exceptions" hype.
Not just hype. Hype would be people giving talks about and talking about how wonderful it was to be freed of runtime exceptions. But I went to elm-lang.org today and right there as the #1 selling point for Elm was "No Runtime Exceptions". In my job, I find myself harping on the fact that when the messaging says one thing and the product delivers something else, at least one of them is wrong and needs to be fixed. So, either the exceptions need to be eliminated from the Elm runtime or the front page of elm-lang.org needs to shift to saying something like "Fewer Runtime Exceptions". One could argue that you just need to avoid writing the Elm code that triggers the exceptions but that same argument would apply to JavaScript. As I said, I would like to promote using Elm but the skeptics have a lot of ammunition for identifying Elm as a technology that seems to over promise and under deliver and that leaves issues hanging. That makes me sad because it makes Elm advocacy a lot harder. Mark -- You received this message because you are subscribed to the Google Groups "Elm Discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
