On Nov 11, 2007, at 10:44 AM, Mark Miller wrote:
Hi Brendan,
There are many individual aspects of the the ES4 proposal that I like,
many things I don't. All of which I hope to enumerate for this list
over time.
That would be great.
It is one thing to sigh with despair at other people's tend
Hi Brendan,
There are many individual aspects of the the ES4 proposal that I like,
many things I don't. All of which I hope to enumerate for this list
over time. But overall my main distress is still the size of the
language.
At
http://weblogs.mozillazine.org/roadmap/archives/2007/11/es4_news_an
On Nov 10, 2007, at 10:08 PM, Brendan Eich wrote:
> On Nov 10, 2007, at 9:52 PM, Mark Miller wrote:
>
>> I'm using "with" here only as an example, to try to understand the
>> nature of the compatibility constraints on the ES4 process.
>
> Compatibility imposes footprint costs, but it also creates
On Nov 10, 2007, at 9:52 PM, Mark Miller wrote:
> What I
> don't understand is: Why can't this switch change other aspects of the
> language being recognized, so long as this doesn't result in a larger
> implementation?
It could. We considered removing "with" from ES4. But as I noted,
migration
On Nov 10, 2007 9:10 PM, Brendan Eich <[EMAIL PROTECTED]> wrote:
> On Nov 10, 2007, at 8:00 PM, Mark Miller wrote:
[out of order]
>> * The intersection of ES3 and ES4 must be approximately as pleasant a
>> programming language as ES3 currently is.
>
> No, the intersection is "ES3 + reality" + tw
On Nov 10, 2007, at 8:00 PM, Mark Miller wrote:
* To prevent these new keywords breaking ES3 compatibility, these
keywords are only recognized when a version attribute on the script
tag says the script is in ES4.
This has happened before, FYI -- from ES1-3 under various vendor
experiment
Hi all,
I've been reading the overview doc on the ES4 proposal. From it,
and from the threads that I've been reading, I'm confused about
the design constraints on the ES4 process. Are the following
statements all accurate:
* We want ES4 to work well on small devices, so size of implementation
i
