[vlangber]

I would argue that Typescript and React or Vue would have been a better solution for the customer. Yes, Elm might be better in some aspects, but I could name quite a few benefits for Typescript as well.

I think the technical reasoning is okayish, but from a business perspective I don't think the customer made a good choice.

[Skinney]

We actually do have react in production as well. The header on our website is a react component, and our app is written in react-native. We also tried out flow for a while.

Elm compiles faster, has better error messages, is a simpler language (so our apps tend to stay simple, so easier to pick up again after some time) and has less churn.

We have experience with other technologies, we just find Elm better :)

[dorian-graph]

> I would argue that Typescript and React or Vue would have been a better solution for the customer. Yes, Elm might be better in some aspects, but I could name quite a few benefits for Typescript as well.

Go on then. ;)

[vlangber]

I would think most people on Hackernews are familiar with Typescript, but some of the benefits from the top of my head:

- Better tooling - Easier to work with existing javascript code - Superset of javascript - Larger community and ecosystem - More developers are familiar with it - Easy Server Side Rendering

[Lio]

I’m someone that only vaguely knows Typescript and doesn’t know Elm at all, so please forgive me if these seem obvious but would you mind expanding on some of your points?

In what way is the Typescript tooling better? i.e. what can you do with it you can’t do with Elm’s tooling?

Also I’m intrigued by the claim of “easier server side rendering” is it difficult to run Elm code on top of node.js?