Updates:
Status: WorkingAsIntended
Comment #17 on issue 264 by christian.plesner.hansen: Allow
__noSuchMethod__ implementations
http://code.google.com/p/v8/issues/detail?id=264
(Disclaimer: I no longer work on v8; this is just my personal opinion).
I agree that having browser vendors be more active in prototyping new
features would be beneficial for the
evolution of the language. However, I also believe that the biggest
problem facing web developers is
browser incompatibility. In a trade off between those two, language
evolution has to lose if it carries
the risk of introducing incompatibilities. Doing controlled experiments,
say adding experimental features
hidden behind a flag or running internal experiments over websites to test
compatibility, that's all fine.
Having vendors implement different semi-formal specifications independently
in the current environment,
with many existing incompatibilities unsolved and ES5 being under
implementation in all camps, is asking
for trouble.
--
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
