在本地主机上运行时，从sitefinity项目中的url中删除解决方案/文件夹名称(Remove solution/folder name from url in sitefinity project while running on localhost)

 在V8中，对象背后的数据结构变化很大： 
 
 
 
 对象命名属性，直接“存储在C结构上” 
 
 
 对象外的命名属性，存储在对象外部的数组中，附加间接 
 
 
 索引属性（属性名称可以转换为整数的属性），存储在对象外部的数组中，但数组索引充当关键字 
 
 
 有序哈希表 
 
 
 命名属性按插入顺序排列，因为隐藏的类演变/过渡最自然。 
 
 索引属性按其实际值顺序排列，因为存储插入顺序会浪费内存。 
 
 如果您受到哈希表的支持，则哈希表会故意伪造与自然优化相同的顺序。 
 
 在其他浏览器中也是如此，因为当数字很小时，在实际的“C数组”中存储索引属性是一个巨大的优化。 可以变化的是索引属性是首先列出还是命名属性。 
 
 该规范通过不定义迭代顺序使得这种优化成为可能，并且V8首先（至少根据该bug线程）来利用它。 
 
 在命名之前列出的索引键（反之亦然）当然是任意的，不会影响任何优化。 

In V8 the data-structures behind an object vary a lot:
 
 
 
In-object named properties, stored directly "on the C struct"
 
 
Out-of-object named properties, stored in an array external to the object, additional indirection
 
 
Indexed properties (properties whose property names can be turned into integers), stored in an array external to the object but the array index acts as the key
 
 
Ordered hash table
 
 
Named properties are in insertion order because that's most natural with the hidden class evolution/transitions.
 
Indexed properties are in their actual value order because it would be a waste of memory to store the insertion order.
 
If you are backed by a hash table, the hash table deliberately fakes the same order that results from the natural optimizations.
 
It is the same in other browsers too because storing indexed properties, when the numbers are small, in an actual "C array" is a huge optimization. What can vary is whether indexed properties are listed first or named properties. 
 
The spec made this optimization possible by not defining iteration order and V8 was first (at least according to that bug thread) to exploit it.
 
Indexed keys being listed before named and vice versa is of course arbitrary and doesn't affect any optimizations.