3 ms·

TC39 has a pretty open process for proposals, so you can help. But “not backwards compatible” won’t fly. “Don’t break the web” is a key part of TC39’s thinking

• rbobby 9y ago
  Haven't they already given up on backwards compatibility with things like => and for..of?
  • phpnode 9y ago
    Those are additive, they don't affect the semantics of code that was written before they were added. That is what is meant by backwards compatibility here - you never need to change existing code because of new features.
    • z3t4 9y ago
      before es6 anything added also did not break existing implementations. eg you could run es5 features in a es4 engine using polyfill and progressive enhancement/degression. maybe its time for ES to add meta and overloading - although with a huge cost of complexity !?
  • BillinghamJ 9y ago
    No? They're both backwards compatible.