depmann

4 ms·

1. 1.▲
   by depmann 6y ago

   1. You are applying the ad-hominem fallacy: calling something a name something doesn't remove its value. The reason I didn't point to this label is to avoid people applying the same fallacy and tuning out before considering the me
2. 2.▲
   by depmann 6y ago

   I would make the exact same argument but with completely the opposite conclusion. Just use type casting which is self documenting and easily maintained. How can using Typescript be considered somehow less complex?
3. 3.▲
   by depmann 6y ago

   This premise is factually true for both TypeScript and Flow. Please explain how you could come to any other conclusion. I researched this 4 years ago, and since then Typescript has added the `--checkJs` option, but it still you to run a se
4. 4.▲
   by depmann 6y ago

   Yes, TS and typecasting can live well together. However, once you combine sensible naming by type and typecasting together, the benefits of TS fade. Then one has to ask: are the remaining benefits worth the expense of running a full TS tra
5. 5.▲
   by depmann 6y ago

   Hi, Author of the Article here :) I do not recommend JSDoc. Instead, typecasting has these advantages: 1. Precise self documenting 2. Much easier to maintain and less verbose (see 1) 3. Requires no external tooling outside of the typecast f