Really, although Elm is young and changing its also simple and strong. Here's the argument:
- do you want runtime errors? - do you want to use something simple or complex? (In a Rich Hickey sense) there strives to be one way to do things. This saves valuable decision time that JavaScript developers are going to have to deal with for the rest of their careers. - do you want something that is ultra easy to train people on? - time traveling debugging (eventually) - no unexpected API changes on library updates? - far easier to test? - etc... Then you want elm. I think the first point alone is worth it. You could even try measuring how many errors you have in your current JavaScript code base as a good metric. -- 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.
