> It's not just type annotations anymore + ES6
How not?
! is just an inline type coercion.
> What if Ecmascript in the future uses ! as an operator for a totally unrelated purpose ?
This seems unlikely because ! is already an operator in JS.
But really, this argument could be made against any operator TS uses. What if ES introduces : as an operator? Or if they introduce some sort of ambiguity with the other myriad type definitions? This is not a new issue, and you shouldn't let null checks drive you away from the language.
In any case, both null checks and decorators are behind flags. The decorators flag is literally called "experimental decorators". So it's not like the TS team is pretending that it's going to be stable forever.