They're similar in the sense that TypeScript and Elm are both programming languages. But different in the features they emphasize. They make and value very different tradeoffs. And so depending on the tradeoffs that make sense for your projects you'd choose one over the other.
React/Angular frontends can be built entirely with Elm and the Elm architecture. With TypeScript you'd still be using React/Angular except you'd be writing it with TypeScript.
That's cool as well. Care to share your reasons why?
Mostly not knowing what I'd use it for. It's just not a language I've invested time in finding out about.
For front-end UI development. Single-page web apps or for little widgets on the page.
What are you building? Elm could be a fit.
Node/Python/PHP APIs, React/Angular Frontends. Some native JS on CMS templated/legacy sites.
Is it similar to how you might use Typescript?
They're similar in the sense that TypeScript and Elm are both programming languages. But different in the features they emphasize. They make and value very different tradeoffs. And so depending on the tradeoffs that make sense for your projects you'd choose one over the other.
React/Angular frontends can be built entirely with Elm and the Elm architecture. With TypeScript you'd still be using React/Angular except you'd be writing it with TypeScript.
Alright I'm in.
The Elm Architecture looks really cool.