4 ms·
JavaScript can't fix the legacy issues because of backwards compatibility. Not in terms of making ES2015 code work on old browsers, but making old code work on
by LukeB_UK 11y ago
JavaScript can't fix the legacy issues because of backwards compatibility. Not in terms of making ES2015 code work on old browsers, but making old code work on new browsers.
- acdha 11y agoI agree with the first sentence but the last part seems incomplete. Were you thinking of the difficulties bridging old and new code running in the same app? I like the idea of an opt-in "use modern" to avoid breaking old code but that would get tedious if you needed to call between old and new code in the same app.
- 1ris 11y agoJavaScript even has "int" and such as reserved keyword. A hole lot of stuff could be fixed using them without breaking any compability.
- outworlder 11y agoCan't we run old code with the old semantics unless otherwise specified? We already have stuff that changes semantics, notably strict mode.