DEV Community

Discussion on: Is TypeScript the future of web development?

 
stereoplegic profile image
Mike Bybee • Edited

If someone can't handle simple type definitions on function parameters and return types

These should be documented anyway. I'd rather enforce the (much simpler, and more necessary) standard comment syntax of JSDOC than that plus a bunch of extra crap which isn't actually part of the language.

Stick with POJO and functional programming if you don't like classes.

Pssst... They're still functions.

They don't have the required discipline or flexibility.

Sounds a lot like someone who not only expects, but insists on one language behaving like another, rather than using the language as designed (if it makes you feel any better, I've long said the same about Python devs and CoffeeScript - just, fortunately, it didn't take off nearly as much... Now, YirgaCheffeScript or SidamoScript? Count me in).

If you've jsdoc'ed your code, you can understand enough of the syntax in like 5 minutes.

2.5 if it's JS. You should be using JSDoc (and linting) anyway.

Thread Thread
 
stereoplegic profile image
Mike Bybee • Edited

But again, to give TS (utilities) some credit: ts-check (which recognizes JSDoc, and can be set for JavaScript) is a fantastic tool while coding in VS Code. I mean that sincerely.

And tsc is great for turning TS codebases into (at least semi-)usable(/fixable) JS/ES.