3 ms·
For me, it's not even about "typing" or even "checking for errors as you type". The killer feature is: almost never having to read library documentation. You ty
by niieani 10y ago
For me, it's not even about "typing" or even "checking for errors as you type". The killer feature is: almost never having to read library documentation. You type the code, and get suggestions for all the properties and methods available, along with all the possible arguments you are supposed to pass. Saves you a TON of time and context switching, so you can focus better on the task at hand.
That alone makes TypeScript worth the trouble IMHO.
- lloyd-christmas 10y ago> You type the code, and get suggestions for all the properties and methods available, along with all the possible arguments you are supposed to pass. Only if the library itself is written in Typescript or the ambient definitions are perfect. Not necessarily a detractor from the language, but still a practical time sink given the current state of external typings. It's definitely getting better, but it's still quite far from a minimal nuisance.
- Roboprog 10y agoThe "intellisense" crowd always kills me with this: I don't really know what this does, but the IDE suggested it and I'm just going to run with it! What could possibly go wrong? This is of course less ridiculous if some documentation about each routine is displayed as you up and down arrow through the choices.