Comment #19 on issue 264 by [email protected]: Allow __noSuchMethod__
implementations
http://code.google.com/p/v8/issues/detail?id=264
I don't see how nightly-build experiements hurt. We won't ship proxies in
Firefox if
the spec looks like it will be changed significantly, or removed
from "Harmony"
status and not in the next ES edition. But if we do ship it and it gets
standardized
soon, that is better for the Web than if we hide support behind a version
flag or
custom build option.
Really, web developers are not going to start using something experimental
unless it
is crucial enough to be worth the development overhead and content forking.
True, open web dependencies on experimental features could happen, but if
they do,
they are important feedback signals to the committee and other vendors. We
in Ecma
TC39 have explicitly stated our preference to do de-facto
over "design-by-committee"
de-jure standardization.
If possible we want to codify de-facto standards that came from pure-JS
libraries,
but if necessary (where you can't bootstrap the needed feature in pure JS)
by vendor
extensions based on harmony:proposals. It's important to have good specs.
It is not
important to shield prototype implementations from large-scale user
testing. Quite
the contrary.
/be
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
