A few weeks ago, Criteolabs hosted the Paris TypeScript Meetup #3 here at our R&D headquarters in the 9th arrondisement of Paris.
In the last 18 months, we’ve started running quite a few new projects using TypeScript. Some people here love it, most people are OK with it, and some people can’t stand it.
Since we had such an array of reactions, we thought it might be interesting to share our experience with the community.
Despite our differences of opinion, we all agreed that if you’re starting a new project and considering using TypeScript, you should consider the following:
- Size of Project: For a small project, maybe not worth the overhead of the project setup.
- Size of Team (#developers): The more developers, the more valuable the “code as documentation” aspect of adding typing.
- Lifetime of Project: For a proof-of-concept type project, the added value of typing may be less than the overhead (see #1 and #2).
- Team Motivation: TypeScript is maturing rapidly, but it’s still a pretty new language. Finding “best practices” or help on stack overflow will be harder, so it helps if you have genuine interest/buy-in from your team.
In addition, after spending three days with Angular 2.0 at the largest Angular conference to-date AngularConnect, we can add that we are more excited about TypeScript than ever…. even our staunchest TypeScript protester, whose response to Angular 2.0/TypeScript was “definitely thrilled”. You may have reservations about using TypeScript with your Angular 1.x app, but there’s no question you’ll want to use it with Angular 2.0. The official line in nearly all of the talks was “this will also work if you’re not using TypeScript” (not the other way around).
Slides from our talk: http://slides.com/cniaulin/do-you-really-want-a-layer-above-your-js#/
Senior Dev Lead, R&DSee Dev Lead roles