i already experienced that earlier with coffeescript.
because javascript is so ubiquitous, everyone has to learn it, and there is a large pool of inexperienced javascript developers.
however, only those who are actually skilled will apply for a position that requires coffeescript or typescript.
I'm most excited about: TypeScript 4.0 supports a promising proposal to add three new assignment operators: &&=, ||=, and ??=.
Which is a nice shortcut for operators I use often.
No huge changes here that I can see, just small steady improvements to an already excellent language.
https://github.com/microsoft/TypeScript/issues/38568 https://github.com/microsoft/TypeScript/pull/32264
Not sure I like this. Can definitely imagine the following being a realistic scenario, and see no reason to disallow it:
class Base {
public num = 42;
}
class Child extends Base {
protected _num = 42;
// no longer allowed in 4.0
public get num() { return this._num; }
public set num(newVal) {
alert(`new num ${newVal}`);
this._num = newVal
}
}
Did I misunderstand something?I love when such "old" feature request is finally added to Typescript. First proposal for it was almost 5 years ago [1]. It really gives hope for other long standing and heavily upvoded feature requests that maybe we'll get them one day :)
We use ts-loader with webpack in transpileOnly mode and a separate tsc invocation for typechecking that runs as a linter i.e noEmit