Announcing TypeScript 2.1 • Hacker News Board

Re: Announcing TypeScript 2.1

#21

Post by nojvek » Wed, Dec 07, 2016, 5:57 PM UTC

Would be so cool if the js engines ignored types like python3.

Then I could just write Typescript and run it on node/browser

Re: Announcing TypeScript 2.1

#22

Post by Guillaume86 » Wed, Dec 07, 2016, 5:58 PM UTC

zdragnar wrote: post #8

It'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.

Not surprising at all, parity with babel language support and ease to switch to typescript easily is very useful. Some features like the spread are not possible without the new features btw.

Re: Announcing TypeScript 2.1

#23

Post by g00gler » Wed, Dec 07, 2016, 6:01 PM UTC

timruffles wrote: post #11

If you still haven't given TypeScript a go as a Javascripter, now is a great time to do so. 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.

I have to second Mr.timruffles. After using TS in a couple of projects I grew to miss it when I couldn't use it.

If you don't like the C#-ness of Typescript, try using Facebook's flow. Typing isn't a magic bullet, typescript isn't even type safe, but it sure makes development easier and your apps more stable.

Re: Announcing TypeScript 2.1

#24

Post by libria » Wed, Dec 07, 2016, 6:01 PM UTC

I like the functionality of

    let merged = { ...foo, ...bar, ...baz };

But I've come to understand ... as variadic parameters in C++, Java and Go. Wish they'd used another token.

Re: Announcing TypeScript 2.1

#25

Post by raphinou » Wed, Dec 07, 2016, 6:02 PM UTC

seattle_spring wrote: post #18

Seems like all of the new features have been available in Flow for quite a while now.

Typescript seems to get a lot more attention (at least on HN). How does Flow progress? How is the community around it? I'm curious to know more as an external to both projects.

Re: Announcing TypeScript 2.1

#26

Post by icholy » Wed, Dec 07, 2016, 6:04 PM UTC

seattle_spring wrote: post #18

Seems like all of the new features have been available in Flow for quite a while now.

The new type system features are: keyof, lookup types, and mapped types. Does flow have even one of these?

Re: Announcing TypeScript 2.1

#27

Post by [deleted] » Wed, Dec 07, 2016, 6:04 PM UTC

seattle_spring wrote: post #18

Seems like all of the new features have been available in Flow for quite a while now.

[deleted]

Re: Announcing TypeScript 2.1

#28

Post by jasonallen » Wed, Dec 07, 2016, 6:04 PM UTC

Feels like Typescript is building (or has built up?) more momentum than Flow.

Re: Announcing TypeScript 2.1

#29

Post by treve » Wed, Dec 07, 2016, 6:07 PM UTC

jasonallen wrote: post #28

Feels like Typescript is building (or has built up?) more momentum than Flow.

I don't think Typescript has ever not been bigger, but could be wrong here.

Re: Announcing TypeScript 2.1

#30

Post by euroclydon » Wed, Dec 07, 2016, 6:12 PM UTC

One thing I never understood with Babel is which features are shimmed in the output JS and which features are re-implemented?

What I means is: I didn't know how to tell Babel which browsers I was targeting, and I'm pretty sure that some of their feature implementations do not feature test the platform before activating, since they were so compiled in. Is that the case?

Also, do you have to tell TypeScript your target runtime for it to it to use it's ES3 async/await logic vs. it's ES2015 (which uses generators), or does it automatically figure it out?