> strict is now true by default
I would still have a full head of hair if this had been the case since the beginning. Nonetheless I am glad that we got here in the end.
> strict is now true by default
I would still have a full head of hair if this had been the case since the beginning. Nonetheless I am glad that we got here in the end.
TypeScript never would’ve taken off if it had been strict from the beginning, it would’ve been just another forgotten gravestone next to Dart and CoffeeScript. I’m not saying those are bad languages, they’re not, but anything other than a very slow and gradual opt-in transition was just a non-starter. It was painful, but TypeScript played the long game.
Many of the strict checks did not even exist when TS was first created.
Some of these missing checks were why Flow was an attractive choice when weighing [Flow vs Typescript][1].
For example, it wasn't until Typescript 2.0 that we got null checks!
- https://www.typescriptlang.org/docs/handbook/release-notes/t...
[1]: https://djcordhose.github.io/flow-vs-typescript/2016_hhjs.ht...I came to point that out too. What an awesome development. I think this will have a meaningful impact on the general quality of TS projects over the coming years.
If it had been, maybe I wouldn't have had to spend years getting buy in for turning on that setting in my team's codebase.
Just use deno
Exactly when do you think demo started.