4 ms·
Does this description of Typescript match up with the experiences of others? Typescript is usually spoken of positively on HN, so I was surprised to see it: >
by neuronexmachina 9y ago
Does this description of Typescript match up with the experiences of others? Typescript is usually spoken of positively on HN, so I was surprised to see it:
> The main thing we didn’t like and we still don’t like about Angular 2 is Typescript. I know Angular 2 can be used with Javascript but again, the decision to use Typescript was already taken and from what I understand, using pure Javascript with Angular 2 is not the ideal way you should be using Angular 2. In any case, getting rid of Typescript meant a full rewrite of the project.
> I didn’t feel Typescript added substantial value and even worse, we noticed that our coding speed was reduced. With Typescript things that were really easy to do on Javascript like defining a simple object were more complicated to do on Typescript. I highly recommend you to read the following articles before you start using Typescript. It is not the right solution for everyone.
- tarr11 9y agoIf "coding speed" is the most important factor, dynamic languages will win over typed languages. Types force you to slow down. But they offer some obvious advantages in the long term [1] Not sure what the poster means by "defining a simple object" being difficult in TS, so it's hard to say. [1] See every static vs dynamic conversation on HN, ever
- vorotato 9y agoThose who don't understand the value of Types are doomed to recreate them in tests.
- mchahn 9y agoWhat do you mean by "recreate types in tests"? Checking for the right results doesn't require any type-checking. If the result is right the type is right.