On Tue, Oct 11, 2011 at 10:08 AM, Brendan Eich <[email protected]> wrote:
> On Oct 11, 2011, at 12:49 PM, John J Barton wrote: > > > We don't know what the standard will be so we need some why to try out > different features. > > That's not how the committee has worked since 2008, and even before then > (pre-Harmony), with a split committee, we still had two groups working on > consensus by drafting proposals and prototyping them. > > The way we try to work is to propose before implementing, including > prototype features. Individual vendors don't deviate from proposals > unilaterally and silently. > > If old proposals were implemented, and then the proposals changed, we may > have some work to do adjusting implementations (certainly true of > SpiderMonkey, and we will do it). But we do not go off on our own, as > individual vendors, and try out features never proposed on the wiki. > You're making something out of nothing. To me Traceur is just exactly what it is: some open source code for a JS to JS compiler written by some good engineers who now seem to be doing something else. If you have a beef with how Google works with the committee, then contact a Google rep on the committee and complain to them. But don't paint the Traceur project as some weird plot to derail your work. It's just like a thousand other open source projects, a risky labor of love, a gift to the community of engineers. > Also, your point in an earlier message about user testing was good. We > can't "do science" to decide what features in the enormous feature-vector > hyperspace to standardize. We won't search well, and user-testing gives > little certain data. We can hope to find obvious usability problems that > were not foreseen. Also interactions with other features (old and new) that > were not anticipated. > > User testing is good but if we're working in Harmony, the harmony:proposals > are the ones to prototype-implement, and edit based on implementation and > user testing. Ecma works by consensus. > > It's hard to keep consensus or achieve it later by doing single-vendor > experiments that seem to blindside the committee, and possibly even the > community. > > This does not mean design by committee. The designers are one or two > champions working on individual proposals. But the proposal work happens in > the open, in plain sight. Mark and Tom's Proxy work is an exemplar. > Well we don't have a Mark and Tom for Traceur. We just have some great source code. If anyone here wants to try to match Traceur up to Ecma consensus, please step up. jjb
_______________________________________________ es-discuss mailing list [email protected] https://mail.mozilla.org/listinfo/es-discuss
