4 ms·

This tool is ridiculous and less than useless. Can't anyone else see how ridiculous of an idea it is to add types automatically? Isn't the whole point of static

This tool is ridiculous and less than useless. Can't anyone else see how ridiculous of an idea it is to add types automatically? Isn't the whole point of static typing to allow the human developer to specify what the types should be? If a machine could resolve the type integrity issue automatically from dynamically typed code (which is what this tool claims to do), why do we need this tool to physically insert type annotations into the code to begin with? I can't believe I even have to explain myself. I thought static typing was meant to protect the code's integrity? Clearly this tool is undeniable proof that static typing exists merely to satisfy human ego and neuroticism and has nothing to do with logical integrity... Since this tool itself supposedly proves that this integrity can be derived automatically from dynamically typed code. This tool is a paradox, a blatant logical contradiction. If this tool does work as advertised, then it proves the uselessness of static typing and thus, by extension, this tools proves its own uselessness. EDIT I removed a potentially offensive remark from my comment. This makes zero sense to me is my point.

ludamad 6y ago
There's no conspiracy here, just TypeScript is now strict enough to need annotation, and the authors deemed it better to work with a valid TS file and annotate from there than loosen that strictness.
KenanSulayman 6y ago
Who hurt you? This project is meant to make developers more efficient and support them in migrating projects to TypeScript. The entire point of TypeScript is to make developers more efficient, too, through clear structuring, types and assistance through its toolchain. Static typing does not protect you from integrity issues. However, it allows you to extend existing code with confidence. I'm not sure if you work in a team, but your general attitude isn't exactly conducive to a constructive, open and efficient working environment.
- cryptica 6y ago
  >> Who hurt you? TypeScript hurt me. >> However, it allows you to extend existing code with confidence This argument is often used and cannot be disproved but the words "with confidence" betray the case for its objectivity. Confidence is a subjective emotion; I can tell you that I feel confident about extending my JavaScript code without TypeScript and you can't argue with that. So this is a subjective argument and my extensive subjective experience of both languages disagrees with the premise. The most innocent explanation that I can come up with is that TypeScript caters to developers who are not good at coding and thus lack confidence in their coding ability. For me, TypeScript has 0 effect on my confidence and the transpilation step makes things more complicated and makes me less productive overall. Testing is the only thing which increases my confidence in the code; nothing else has any effect on my confidence levels... Not even the language (and I used many over the years). This leads me to think that the confidence which TS gives developers is an illusion, I remember a time when I was younger and used to harbor such illusions about static typing so I'm just drawing projections about other people from my own experience. And yes, your first observation about me is absolutely correct, my skills as a developer have been thoroughly battle-tested and this has hurt me. To me, the existence of this tool is like reliving a past trauma. >> I'm not sure if you work in a team, but your general attitude isn't exactly conducive to a constructive, open and efficient working environment. My team is very productive (I'm CTO). We're productive because we're pragmatic. We don't use TypeScript because we're pragmatic. I don't have to resort to this attitude because my team members were carefully selected for having high level critical thinking and so they wouldn't make such big mistakes as creating this tool.
  - claytongulick 6y ago
    I'm glad that someone else is willing to point out that the TS emperor has no clothes. I see teams waste so much time on type garbage that serves no useful purpose, some code bases up to 70% of the code is all type stuff. I guess it looks good for pseudo productivity when sprint planning though. Perfect example of activity over achievement.
    - deleted 6y ago
      [deleted]

ludamad 6y ago

There's no conspiracy here, just TypeScript is now strict enough to need annotation, and the authors deemed it better to work with a valid TS file and annotate from there than loosen that strictness.

KenanSulayman 6y ago

Who hurt you? This project is meant to make developers more efficient and support them in migrating projects to TypeScript. The entire point of TypeScript is to make developers more efficient, too, through clear structuring, types and assistance through its toolchain. Static typing does not protect you from integrity issues. However, it allows you to extend existing code with confidence. I'm not sure if you work in a team, but your general attitude isn't exactly conducive to a constructive, open and efficient working environment.

cryptica 6y ago
>> Who hurt you? TypeScript hurt me. >> However, it allows you to extend existing code with confidence This argument is often used and cannot be disproved but the words "with confidence" betray the case for its objectivity. Confidence is a subjective emotion; I can tell you that I feel confident about extending my JavaScript code without TypeScript and you can't argue with that. So this is a subjective argument and my extensive subjective experience of both languages disagrees with the premise. The most innocent explanation that I can come up with is that TypeScript caters to developers who are not good at coding and thus lack confidence in their coding ability. For me, TypeScript has 0 effect on my confidence and the transpilation step makes things more complicated and makes me less productive overall. Testing is the only thing which increases my confidence in the code; nothing else has any effect on my confidence levels... Not even the language (and I used many over the years). This leads me to think that the confidence which TS gives developers is an illusion, I remember a time when I was younger and used to harbor such illusions about static typing so I'm just drawing projections about other people from my own experience. And yes, your first observation about me is absolutely correct, my skills as a developer have been thoroughly battle-tested and this has hurt me. To me, the existence of this tool is like reliving a past trauma. >> I'm not sure if you work in a team, but your general attitude isn't exactly conducive to a constructive, open and efficient working environment. My team is very productive (I'm CTO). We're productive because we're pragmatic. We don't use TypeScript because we're pragmatic. I don't have to resort to this attitude because my team members were carefully selected for having high level critical thinking and so they wouldn't make such big mistakes as creating this tool.
- claytongulick 6y ago
  I'm glad that someone else is willing to point out that the TS emperor has no clothes. I see teams waste so much time on type garbage that serves no useful purpose, some code bases up to 70% of the code is all type stuff. I guess it looks good for pseudo productivity when sprint planning though. Perfect example of activity over achievement.
  - deleted 6y ago
    [deleted]