7 ms·
I think this is more of a permission feature for objects than a performance optimization. I think this `freezing/unfreezing` of objects only makes sense in an e
by mlLK 17y ago
I think this is more of a permission feature for objects than a performance optimization. I think this `freezing/unfreezing` of objects only makes sense in an environment [or application] where objects and resources are being shared by more than one user or process. . .much like GNOME locks files in /tmp according to processes running on some other user's session.
- jeresig 17y agoIt's important to realize that once an object or property is "locked" (e.g. prevent extensibility on an object - most likely by being sealed or frozen) it cannot be "unlocked" - it's that way for as long as the object exists. This is done intentionally in order to prevent other code from unlocking it and then modifying it.