Comment #75 on issue 235 by [email protected]: Support the Javascript E4X extension
http://code.google.com/p/v8/issues/detail?id=235
I'm thinking about filing a seperate bug report stating the V8 Feature Request process is malfunctioning. Like stated in comment #71, whether this feature is added or not,100 stars deserves some form of recognition in the form a a status update, opinion or a simple 'it's available in the next update'.
That Google sees no use for E4X in Chrome is bad enough, but now V8 is being used in other projects the issues propagates.
Like node.js, which out of the box lacks usable XML support and literally screams for E4X. The team that make it are pointing to V8 as it's the javascript engine on duty, and trying to add it themselves to a beats like V8 is too big of a side project. So for whatever project V8 is used, we're left with whatever the community of that project can come up with. So besides not using viable standards V8 now has the effect of promoting standards fragmentation.
All-in-all it feels like there's political games being played between Google and EMCA, or Google & Firefox or Google & XML or whatever. Evil games.
-- v8-dev mailing list [email protected] http://groups.google.com/group/v8-dev
