Ah. Gotcha. Yes, that's a good point. But even though such changes are
costly and less needed by ES7, I expect ES7 will nevertheless have
some further syntax enhancements that don't work on ES6. The main
example is the minimality of min-max classes, These really really need
to be made more usable in ES7.
On Mon, Dec 3, 2012 at 6:28 PM, David Herman <dher...@mozilla.com> wrote:
> On Dec 3, 2012, at 6:27 PM, "Mark S. Miller" <erig...@google.com> wrote:
>
>> On Mon, Dec 3, 2012 at 6:14 PM, Brandon Benvie
>> <bran...@brandonbenvie.com> wrote:
>>> I understand that there's limitations on what can be packed into this
>>> release and in particular this proposal pushes the limits. But I don't buy
>>> the ES7-is-around-the-corner wager for two reasons.
>>>
>>> The first reason is that I believe it's likely going to be a lot harder to
>>> get syntax changes into ES7 than for ES6. ES6 is basically the cruise boat
>>> to new syntax and once that boat sets sail it's going to be another decade
>>> before anyone wants to screw around with breaking syntax changes.
>>
>> What are the breaking syntax changes in ES6?
>
> He's not using the term the way you and I do. :) He means using new syntax
> breaks when run on old browsers.
>
> Dave
>
--
Cheers,
--MarkM
_______________________________________________
es-discuss mailing list
es-discuss@mozilla.org
https://mail.mozilla.org/listinfo/es-discuss
