Hey Elmos, I've finally gotten an opportunity to pitch Elm to my fairly large dev team. I feel like I'm prepared to make the case for it against a lot of objections: i.e. how will we learn yet another programming language, do we really need something that never throws exceptions, etc. etc.
The one thing I'm not really sure I'm prepared to answer is how I can be sure that Elm isn't just another CoffeeScript or Dart, and in 2 or 3 years we'll have an impossible time hiring anyone who knows how to use it because everyone's going to go back to JavaScript. How do I convince Elm skeptics that this thing is here to stay? I can do a great job of incorporating a small bit of Elm code into our stack to show how great it is, but they won't even let me merge it into prod unless I can make the case for its longevity. -- 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 elm-discuss+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
