In a way I agree (despite the old gmail name :) in the same way that I prefer Erlang, Python, and Javascript over Java. I do think XML is here to stay though as the use cases do not completely overlap JSON use cases. AFAIK XML is designed to convey meaning in a structured way vs JSON, which is designed to convey data structure. A place where XML truly shines vs JSON is document transformation/query via XSLT/ XPATH. There are many areas where JSON shines over XML.
But more importantly there are a lot of clients whose software uses XML, there's a lot of commercial software that uses XML, and there's a lot of libraries that implement useful XML technologies - in the same way that many clients software is built with Java and many useful libraries are in Java. So JSON is great and very useful but E4X is needed for the times when external forces are requiring us to use XML. If not E4X then I think at least DOM2 (preferably DOM3) support is needed. On Nov 25, 11:37 am, [email protected] wrote: > Comment #6 on issue 235 by erik.corry: Support the Javascript E4X > extensionhttp://code.google.com/p/v8/issues/detail?id=235 > > I think the alternative solution that works is json. > > -- > 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 -~----------~----~----~----~------~----~------~--~---
