When to Use TypeScript – A Detailed Guide Through Common Scenarios

Re:When to Use TypeScript – A Detailed Guide Through Common ... by mattmanser on Sunday April 07, 2019 @02:24PM (#19598799)

It doesn't as you've already made that decision when adding a property. Almost always you get rid of the property entirely and replace it with a new one (and the type), you extremely rarely change the type.

And you will almost always know what type a property needs to be. Name? string. IsActive? boolean. Last modified? Date. Etc.

Also typescript just has number, so you're not even faffing around thinking "int, float, long, double, decimal, unsigned, signed" when adding a number. Although this is ultimately a bad thing.

[ Parent | on HN ]

Re:When to Use TypeScript – A Detailed Guide Through Common ... by mixmastamyk on Sunday April 07, 2019 @02:45PM (#19598982)

It does, I’m talking more about module/system architecture than properties. I might go through three designs on a brand new project and futzing with types and tests while factoring it is an inefficient use of time. Waiting until satisfied with design is my advantage.

[ Parent | on HN ]