News for hackers. Stuff that matters.

A comment on How porting to TypeScript solved our API woes. Parent comment

Re:How porting to TypeScript solved our API woes by salmonellaeater on Wednesday April 08, 2020 @05:14PM (#22817233)
> You lose flexibility when suddenly everything is locked to each other by name.

This is only true of nominally typed languages (such as... most typed languages). TypeScript is a notable exception: values just have to have the same property names and types and they'll fit. The language's philosophy is basically to describe the way people write JS rather than prescribe how people should write it, so idiomatic JS is usually easy to express in TypeScript.

[ Parent | on HN ]
Re:How porting to TypeScript solved our API woes by desert_boi on Wednesday April 08, 2020 @09:27PM (#22818992)
There are some caveats to the structural type system in TypeScript. The most glaring of which is multiple versions of the same typings will not align with each other regardless of sharing the same shape.
[ Parent | on HN ]