Comment #63 on issue 164 by [email protected]: Wrong order in Object properties interation
http://code.google.com/p/v8/issues/detail?id=164
@pcxunlimited: I totally agree on this one. Since when IE has been the flag to follow. As developer we make sure our code works first on the "other standard" browsers and later we test if this works on IE many flavors and start to put all kinds of hacks to be compatible. This is done only because we have no choice that Microsoft shoveled IE on every Windows computer. Now we will need to add Chrome and Opera on this pool too. I had not done it yet to show our clients how ugly thinks can get using the wrong browser and probably we will not do it as there is not enough market share from Chrome yet.
@charles.kendrick: As you asserted, this is not a bug, but it is what developers had been used to work. Human can eat meat, feed somebody for years with cook meat, then one day day change it to raw meat, what is it going to be the reaction? This is fault of ECMA for not be specific on this standard and now our meat as we know is mess up.
On Issue 37404 Comment 16, I went on detail that the real issue is that data coming from other places were we have not control and the possibility to "taint" the object properties before they send on JSON messages for a Chrome hack to work. If I receive a "clean" JSON, I cannot use the build JSON function, I have to code my own JSON parser to taint the properties before they go to a real object. Then, before send or commit any data, it must be untainted of hacks. The speed gained on V8, it will be lost on workarounds.
The most disturbing fact is that any other languages that I have at my reach to test (correct me if there is any other obscure language that doesn't do it), creates and keep properties on the same order that were inserted.
The people that care of this issue could fight on ECMA to clear up this loose end, make their opinion with Opera and Microsoft (as it's done here), but we should start somewhere where people is listening.
I stopped using Chrome as my main browser, I use it only to read my mail. We also stopped pushing Google Chrome Frame from our sites as it's having this same problem due to the V8 guts. My main browser and all my developer team is back to Firefox. Too bad, I really liked to keep driving this "Chrome V8" fast bi-turbo car, but it keep messing up with anything I put on the trunk.
-- v8-dev mailing list [email protected] http://groups.google.com/group/v8-dev
