rodneon

5 ms·

1. 1.▲
   by rodneon 8y ago

   This is only a problem when you remove properties from an object. Ok, in this particular case, I buy your theory... but I'll ask again: is all the added cruft really worth this small safety? I mean, when you say "when the types
2. 2.▲
   by rodneon 8y ago

   > potential runtime errors (...) before they (...) happen in production I seriously can't think of an example of this. If all testing is done properly, from unit testing to integration, etc, the compile time safety for front end dev
3. 3.▲
   by rodneon 8y ago

   Those have been my thoughts exactly, except I might need to buckle down and use Typescript because the devs at work favor it. I don't want to hate coding in Typescript, which is why I posted this Ask HN. I still wouldn't use it
4. 4.▲
   by rodneon 8y ago

   Mainly create-react-app, styled-components, react-styleguidist (which uses react-docgen). I'm okay with writing .d.ts files for my React components, but trying to develop these components in this ecosystem... oof.
5. 5.▲
   by rodneon 8y ago

   The refactoring bit is almost convincing enough for me. I'm a front-end developer with a strong background in JavaScript and React. They say Typescript is a superset of JavaScript, but I disagree. I feel like I can't write JavaS
6. 6.▲
   Ask HN: Convince me that TypeScript is better than JavaScript

   6 points by rodneon 8y ago|13 comments