News for hackers. Stuff that matters.
Re:Why Angular 2 Switched to TypeScript by dang on Sunday July 24, 2016 @02:03PM (#12154075)
Here's one of many examples: when you're defining types you have to think of names for them. That's a high-energy mental operation.
Re:Why Angular 2 Switched to TypeScript by domlebo70 on Monday July 25, 2016 @04:22AM (#12157223)
Interesting. Can you give me some more examples?
Re:Why Angular 2 Switched to TypeScript by dang on Monday July 25, 2016 @01:28PM (#12160137)
Another is that you get a slower interactive development cycle because you have more things to do before your code can run.

For example, some portion of your program may be half-baked because you haven't worked out its types yet, or maybe you've changed a type but haven't yet updated the rest of the program. If you want to play with your program interactively to find something out about the work in progress, now you can't, because your program isn't currently 'correct', i.e. it isn't self-consistent.

This adds drag to the development process. First, you have more work to do. Second, it breaks flow: you must switch your attention to something extraneous, breaking your concentration on what you were doing. Third, it gets you in the habit of satisfying the machine rather than thinking about the problem you're trying to solve.