Elm in Production: 25K Lines Later

Re:Elm in Production: 25K Lines Later by fbonetti on Monday July 31, 2017 @01:10PM (#14893850)

Cons of using Typescript:

* Lack of purity. You can unintentionally trigger side effects from a function that's a supposed to simply return a value.

    function add(x: number, y: number): number {
      fireTheMissiles()
      return x + y
    }

* It's impossible to validate that external JSON data is the correct type at runtime. If a JSON API returns something weird, you're going to get a runtime error.

[ Parent | on HN ]

Re:Elm in Production: 25K Lines Later by jnbiche on Monday July 31, 2017 @01:28PM (#14894085)

> Lack of purity.

I agree. Which is why I said "many if not most" benefits, not all benefits.

> It's impossible to validate that external JSON data is the correct type at runtime.

Not sure I understand what you're saying. Of course you'll get a runtime error if your external JSON is the wrong type, what else could you do? Accept the data and enter an inconsistent state?

However, similar to the Elm JSON validation, in Typescript and Flow, you can write schemas to to runtime validation of external JSON. There are multiple libraries for this.

[ Parent | on HN ]