On Saturday, November 5, 2016 at 10:01:42 PM UTC, Zacqary Adam Xeper wrote: > > 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. >
I can understand their skepticism because its a fast moving space and a lot of things have come and gone... but you have to take risks and try new stuff too or you get left behind. So I'd pitch it as a risk/reward decision and try to mitigate the risks for them: * It may be hard to find dev talent for a minor language - but its easy (fun even) to learn. You may also end up attracting better talent - those who are prepared to learn new stuff and have the kind of mind that adapts and enjoys learning. * It may be hard to find people to maintain the codebase long term - UI codebases are re-written from scratch often enough that we even start to think of them as 'throw away code', so how can you even be sure an ember/angular/react UI isn't going to fail to make it long term? Also Elm code is very nice to maintain, the compiler really helps you. Maintaining an Elm codebase is a fraction of the effort of JS. * Elm may completely die off - but not until something that incorporates the same ideas but pulls it off even better pushes Elm to the side. In which case effort invested in Elm will still be of value to your company - in fact you will be ahead of the competition. I hope you succeed, let us know the outcome. -- 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.
