> Convincing other developers typescript has value and isn't javascript's weird ugly nephew is an uphill struggle. I feel the same way about Elm, F# and Fable,

> Convincing other developers typescript has value and isn't javascript's weird ugly nephew is an uphill struggle. I feel the same way about Elm, F# and Fable, Facebook's ReasonML, and any other language that has an ML type system and compiles to javascript. I think the value becomes more apparent when: a) you work in a large codebase and have to refactor either a large swath of code and/or a critical piece of logic and b) you need to make illegal states unrepresentable. In both cases, I have found having a compiled, ml-typed language extremely helpful. I think for both Typescript or an ML language, having immutable non-nullable types by default really cuts down on complexity - instead of having to specify everything that's immutable with something like a `const` keyword, you instead have to specifically point out which attritibutes on a type are mutable. That's a small win but has huge benefits - especially when you're trying to debug code. That's just my two cents anyway.