W3C home > Mailing lists > Public > public-script-coord@w3.org > October to December 2009

Re: Conflicts between W3C specs and ES5?

From: Brendan Eich <brendan@mozilla.org>
Date: Tue, 17 Nov 2009 19:08:40 -0800
Cc: James Graham <jgraham@opera.com>, "Mark S. Miller" <erights@google.com>, public-script-coord@w3.org
Message-Id: <5C2DDDD0-15A9-4B27-9FAF-8D29DB48C48D@mozilla.org>
To: Maciej Stachowiak <mjs@apple.com>
On Nov 17, 2009, at 6:41 PM, Maciej Stachowiak wrote:

>> I don't think I'm misreading your message. Recrimination is not the  
>> issue. The issue is de-facto standard codification, however  
>> distasteful, vs. a cleaner standard that could supersede the de- 
>> facto standard. You framed this pretty well with __proto__ as the  
>> concrete case.
>
> I wouldn't even frame it as a versus.

I would because in my experience you never have time to "spec both  
ways", and the tasteful folks who turn green at the legacy try to  
block it. And perhaps they are right to do so, for reasons Garrett  
gave. It's not always best to "do both".

Ok, enough from me on this thread. It helped point out a few things we  
should work on in TC39:

* The two-way comment hiding hack, if we get the needed help and agree  
on its normative status.
* Something to address the "global object on scope chain vs. |this| in  
global code" issue (known but the discussion here moved it along).
* Date.UTC bug (to be file).

Anything else?

/be
Received on Wednesday, 18 November 2009 03:09:51 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 8 May 2013 19:30:02 UTC