Whether you end up adopting it or not, it's interesting to get the types out of your mind and into the code. The first time you feel the speed/confidence of refactoring with accurate 'Find usages', you'll decide if the undeniable overhead of types is worth it.
Announcing TypeScript 2.1
11–20 of 226 posts
Re: Announcing TypeScript 2.1
#12Re: Announcing TypeScript 2.1
#13It's interesting to me that all of the initial reactions I've seen to this announcement have been around the introduction of async and object spread, which are available with babel, but the typescript specific features such as mapped types are completely ignored. I don't really have any particular meaning behind that observation, only that it tickled my funny bone a little bit.
Re: Announcing TypeScript 2.1
#14It's interesting to me that all of the initial reactions I've seen to this announcement have been around the introduction of async and object spread, which are available with babel, but the typescript specific features such as mapped types are completely ignored. I don't really have any particular meaning behind that observation, only that it tickled my funny bone a little bit.
That means that when using object rest/spread, we didn't want to just ship an experience where type type is effectively `any`, leading users to be frustrated if they make an error.
With async/await, we had to rewrite our emit pipeline, which meant that we needed to keep parity in both output as well as time to emit. The investment has shown, and TypeScript is still extremely fast.
We're always willing to think about different approaches, but those are some of the rationales here.
Re: Announcing TypeScript 2.1
#15Re: Announcing TypeScript 2.1
#16Re: Announcing TypeScript 2.1
#17" We spread ourselves thin, but this is the moment you’ve been await ing – TypeScript 2.1 is here! "
Re: Announcing TypeScript 2.1
#18Re: Announcing TypeScript 2.1
#19It's interesting to me that all of the initial reactions I've seen to this announcement have been around the introduction of async and object spread, which are available with babel, but the typescript specific features such as mapped types are completely ignored. I don't really have any particular meaning behind that observation, only that it tickled my funny bone a little bit.
Re: Announcing TypeScript 2.1
#20Seems like all of the new features have been available in Flow for quite a while now.