3 ms·
I was writing a biggish weekend project. It was mostly client-side logic with a FireBase backend. I developed the first prototype in pure JS and there were som
by hrjet 13y ago
I was writing a biggish weekend project. It was mostly client-side logic with a FireBase backend.
I developed the first prototype in pure JS and there were some bugs (due to me being new to this FireBase model, and some hastily developed code).
I then converted the whole thing to TypeScript, because I prefer static typing. It took some time to setup: upgrading to the latest nodejs, collecting all type definitions for popular libraries, etc. The DefinitelyTyped[1] library is a great resource. But there were some warts in it. I had to make some PRs to this library for some missing methods in jQuery.
But right after finishing the setup, I was able to find and fix a complicated sequencing bug. That alone was worth the trouble of the setup cost.
I then tried using TypeScript for another project (this one had a licensed IDEA available). Here the setup cost was even lower. There are plugins available for Typescript in IDEA. Though I couldn't convince everyone in the team to switch to TypeScript.
This was back before they added generics support. Now that generics is added, I think there is hardly any excuse left to not use TypeScript (or a similar alternative).
What would make TypeScript awesome is support from more IDEs (Eclipse especially).
[1](https://github.com/borisyankov/DefinitelyTyped https://github.com/borisyankov/DefinitelyTyped)
- yareally 13y ago> What would make TypeScript awesome is support from more IDEs (Eclipse especially). There exists a plugin for eclipse, but I have never tried it. I'm mostly an Intellij IDEA user. http://marketplace.eclipse.org/content/typescript http://marketplace.eclipse.org/content/typescript
- santialbo 13y agoI just wish they update the built-in code analysis to use TypeScript 0.9. I don't like having to use outdated type definitions.