News for hackers. Stuff that matters.

A comment on Full-Stack TypeScript, React, Apollo, and Node Example. Parent comment

Re:Full-Stack TypeScript, React, Apollo, and Node Example by jefflombardjr on Wednesday May 15, 2019 @01:30PM (#19921744)
This 100%. I would also add that it seems alot of companies have been substituting type checking for a proper testing strategy. Eric Elliot goes into great length about this in this article: https://medium.com/javascript-scene/the-typescript-tax-132ff...

I'm a little disappointed/surprised flow is viewed by some as a pet project by Facebook, I really think it is a great type checking tool that works nicely with other tooling.

[ Parent | on HN ]
Re:Full-Stack TypeScript, React, Apollo, and Node Example by ng12 on Wednesday May 15, 2019 @02:55PM (#19922548)
This is my least favorite article about TypeScript. It's chock-full of misleading tidbits and questionable interpretations of cited material. The HN discussion on the article is pretty illuminating: https://news.ycombinator.com/item?id=18977700

Flow was built for a very specific usecase: incrementally adding types to an existing untyped project. TypeScript is better for almost everything else.

[ Parent | on HN ]
Re:Full-Stack TypeScript, React, Apollo, and Node Example by jefflombardjr on Wednesday May 15, 2019 @03:22PM (#19922792)
Ohh yeah great discussions there.

I see now, that it's not about which is better, more just different approaches thanks!

[ Parent | on HN ]