There is another one from "Smashing Magazine" [1], I think it's written better :
> In quite a few discussions online about reclaiming memory in JavaScript, the delete keyword is brought up, as although it was supposed to be used for just removing keys from a map, some developers think you can force de-referencing using it. Avoid using delete if you can. In the below example, delete o.x does a lot more harm than good behind the scenes, as it changes o‘s hidden class and makes it a generic slow object.
Although it's from 3 years ago it looks decent. The comments below are even more interesting than the article.
> In quite a few discussions online about reclaiming memory in JavaScript, the delete keyword is brought up, as although it was supposed to be used for just removing keys from a map, some developers think you can force de-referencing using it. Avoid using delete if you can. In the below example, delete o.x does a lot more harm than good behind the scenes, as it changes o‘s hidden class and makes it a generic slow object.
Although it's from 3 years ago it looks decent. The comments below are even more interesting than the article.
[1] : http://www.smashingmagazine.com/2012/11/05/writing-fast-memo...