I got to program in TypeScript (v0.8) for two years. It definitely facilitated making a large scale application more robust and reliable.
The nice thing about it was getting ES6 features on ES3 & ES5 engines. Plus static typing.
The disappointing thing about it was it not being CoffeeScript. (Or more to my liking, the abandoned GorillaScript, which was a more well thought out kind of CoffeeScript. In my opinion.)
These days, we have ES6. Takes a bit of the new car smell out of TypeScript. (Albeit it without static typing. Yet. That may come someday.)
Personally, I'm waiting for Elm 1.0.
In the meantime, I'm back in C++ land. (Ow ow ow.)
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I got to program in TypeScript (v0.8) for two years. It definitely facilitated making a large scale application more robust and reliable.
The nice thing about it was getting ES6 features on ES3 & ES5 engines. Plus static typing.
The disappointing thing about it was it not being CoffeeScript. (Or more to my liking, the abandoned GorillaScript, which was a more well thought out kind of CoffeeScript. In my opinion.)
These days, we have ES6. Takes a bit of the new car smell out of TypeScript. (Albeit it without static typing. Yet. That may come someday.)
Personally, I'm waiting for Elm 1.0.
In the meantime, I'm back in C++ land. (Ow ow ow.)