3 ms·
> Why we shouldn't? Because we (as in browser vendors) can't just break compatibility with all the websites that use strict mode today OK, fair enough. That w
by eric_bullington 12y ago
> Why we shouldn't? Because we (as in browser vendors) can't just break compatibility with all the websites that use strict mode today
OK, fair enough. That was admittedly a glib comment on my part. However, if JS ever wants to be more than a compilation/transpilation target in the long run, it will need to face this challenge and come up with a solution.
Static typing is a definite solution, but I'm skeptical that this will happen in ES7 (or perhaps I just don't want to get my hopes up).
- gsnedders 12y agoSome form of gradual typing is almost certain to reach ES eventually. I don't think anyone is really against it. Whether that goes far enough to make everyone happy… well, it probably won't. But I'm somewhat hopeful about all the research being done around gradual typing, and around TypeScript by MSR in particular that we'll end up with something truly useful and that solves 99% of the use-cases.