TypeScript 3.7 • Hacker News Board

Re: TypeScript 3.7

#11

Post by wwwigham » Tue, Nov 05, 2019, 7:25 PM UTC

vosper wrote: post #8

bobbytherobot wrote: post #6

Earlier quoted context omitted.

How do you handle other language - including JavaScript - updates for your team?

Javascript doesn't change at anything like the pace that TypeScript does, so it hasn't been much of a hassle. But even so we (like many teams with large codebases, I suspect) have callbacks, promises, and async/await all mixed together, depending on when the code was (re)written. It's on our list.

Javascript formally releases once a year, but individual feature adoption in browsers is totally separate from that, and happens.... whenever they feel like it. v8 (chrome's js engine) doesn't have a set release schedule, but has already had 6 formal minor releases this year, each partially adopting some new JS runtime features, all of which have already shipped to chrome.

At our current pace, we formally release 4 times a year, for reference, which is actually a far cry from the more continuous deployment browser vendors currently have setup.

The main difference is that most people kinda ignore new JavaScript stuff for awhile until it trends or gains sufficient rollout. It's an interesting world - I can't really say that people are actually JavaScript version aware, beyond, maybe, what compatibility presets @babel/preset-env gives them.

Re: TypeScript 3.7

#12

Post by WorldMaker » Tue, Nov 05, 2019, 8:07 PM UTC

vosper wrote: post #3

What's the end state for TypeScript? Does it one day become feature complete and slow down? One of the frustrating things about trying to find help with TS today as a beginner is the plethora of SO and blog posts talking about much older versions. If you're lucky there'll be some comment "As of 2.6 you can now do ...", but even 2.6 is a lot of versions back - how do I know that's still the best way to do it in 3.7? I…

> how do I know that's still the best way to do it in 3.7?

Maybe don't worry about the "best" way to do something and use what works? Typescript has really good backward compatibility, it's very rare for something to stop working that previously worked. If it turns out there is an easier way to do something, you'll likely have reason to want to learn it, but at least in my experience with Typescript you'll rarely find a "need" to learn it or your code will break.

Re: TypeScript 3.7

#13

Post by dashwav » Tue, Nov 05, 2019, 10:07 PM UTC

I really like the new optional operator, this might be what gets me to bite the bullet and start moving some of my projects over to typescript - dealing with potential undefined objects in those chains is one of the things I actively dislike about writing in vanilla Javascript.

Re: TypeScript 3.7

#14

Post by simlevesque » Tue, Nov 05, 2019, 10:09 PM UTC

dashwav wrote: post #13

I really like the new optional operator, this might be what gets me to bite the bullet and start moving some of my projects over to typescript - dealing with potential undefined objects in those chains is one of the things I actively dislike about writing in vanilla Javascript.

You won't regret it ! It helps me every day. Just be sure to not be too strict in your tsconfig.json in the beginning.

edit: I'm refering to "noImplicit*" configuration.

Re: TypeScript 3.7

#15

Post by notus » Tue, Nov 05, 2019, 10:10 PM UTC

dashwav wrote: post #13

I really like the new optional operator, this might be what gets me to bite the bullet and start moving some of my projects over to typescript - dealing with potential undefined objects in those chains is one of the things I actively dislike about writing in vanilla Javascript.

I just use lodash get when I access object properties

Re: TypeScript 3.7

#16

Post by tomconroy » Tue, Nov 05, 2019, 10:13 PM UTC

notus wrote: post #15

dashwav wrote: post #13

I really like the new optional operator, this might be what gets me to bite the bullet and start moving some of my projects over to typescript - dealing with potential undefined objects in those chains is one of the things I actively dislike about writing in vanilla Javascript.

I just use lodash get when I access object properties

`get` will destroy type inference, there's no workaround. Your output types are always `any`. The new optional chaining fixes that problem, giving you the same terseness as `get`

Re: TypeScript 3.7

#17

Post by AgentME » Tue, Nov 05, 2019, 10:14 PM UTC

simlevesque wrote: post #14

dashwav wrote: post #13

I really like the new optional operator, this might be what gets me to bite the bullet and start moving some of my projects over to typescript - dealing with potential undefined objects in those chains is one of the things I actively dislike about writing in vanilla Javascript.

You won't regret it ! It helps me every day. Just be sure to not be too strict in your tsconfig.json in the beginning. edit: I'm refering to "noImplicit*" configuration.

>Just be sure to not be too strict in your tsconfig.json in the beginning.

Do you mean to avoid using the "strict" rule, or are you referring to other rules? My number one Typescript suggestion is to make sure you start with "strict": true in your tsconfig.json to be sure your code has nullability correctly enforced.

Re: TypeScript 3.7

#18

Post by simlevesque » Tue, Nov 05, 2019, 10:16 PM UTC

AgentME wrote: post #17

simlevesque wrote: post #14

Earlier quoted context omitted.

You won't regret it ! It helps me every day. Just be sure to not be too strict in your tsconfig.json in the beginning. edit: I'm refering to "noImplicit*" configuration.

>Just be sure to not be too strict in your tsconfig.json in the beginning. Do you mean to avoid using the "strict" rule, or are you referring to other rules? My number one Typescript suggestion is to make sure you start with "strict": true in your tsconfig.json to be sure your code has nullability correctly enforced.

I'm talking about "noImplicitAny", "noImplicitReturns", "noImplicitThis"... they get in my way when I'm editing. When I'm about to push my code I activate them back.

Re: TypeScript 3.7

#19

Post by alipang » Tue, Nov 05, 2019, 10:21 PM UTC

Great incremental release.

Typescript really isn't the most exciting language, but it's very very helpful. Compared to regular javascript it saves me a lot of time, and so many pains and headaches every day.

Re: TypeScript 3.7

#20

Post by nerdkid93 » Tue, Nov 05, 2019, 10:22 PM UTC

notus wrote: post #15

dashwav wrote: post #13

I really like the new optional operator, this might be what gets me to bite the bullet and start moving some of my projects over to typescript - dealing with potential undefined objects in those chains is one of the things I actively dislike about writing in vanilla Javascript.

I just use lodash get when I access object properties

TS 3.7 obviates the need for using `lodash.get` or `just-safe-get`, but it does so in a way that preserves the type of your object