There's an article by Paul Graham, pre-Y-combinator, that may be relevant: http://www.paulgraham.com/avg.html
In my own paraphrasing, the average startup fails. So if you're a startup, you should be *seeking out* technical risks that you think will pay off. If I was in a startup, especially one lacking in front-end programmers, I think Elm is a strong choice. But the more mature your company is, the more Elm's immaturity should bother you. That being said, I think that one of Elm's big advantages is that it's small. You can teach a few JS/Ruby/Python devs the stateless parts of the language in an hour, and TEA in another, pair for a few days, and you'll know enough to be dangerous. There's no separate templating language, no routing DSL, and no magic filename munging. Contrast trying to port an Angular 1.x + CoffeScript app to React+JSX+Redux+ES6.... -- 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.
