How Good C# Habits can Encourage Bad JavaScript Habits

Re:How Good C# Habits can Encourage Bad JavaScript Habits by btilly on Thursday October 07, 2010 @11:00PM (#1770416)

Also, if you're dealing with DOM, you might want to avoid anonymous functions and closures as IE tends to not do proper garbage collection within closures and leak an awful lot of memory that doesn't get freed even after you visited another page.

To the best of my knowledge this was fixed in IE 7. Therefore I consider having such leaks on the general internet to be an underhanded service. Anything that leaves IE 6 usable but less pleasant encourages people to migrate to something better. ;-)

[ Parent | on HN ]

Re:How Good C# Habits can Encourage Bad JavaScript Habits by DrJokepu on Friday October 08, 2010 @05:10AM (#1771073)

It wasn't completely fixed in IE7, unfortunately:

" However, as some web developers have pointed out, those changes don’t solve the problem entirely. IE still leaves behind anything not attached to the tree when we tear down the markup. In addition, sites that users keep open for extended periods of time, such as Web-based mail, can still cause IE’s memory usage to continually grow if the site doesn’t take care to avoid the leak patterns."

http://blogs.msdn.com/b/ie/archive/2007/11/29/tools-for-dete...

It's still a major pain in the back.

[ Parent | on HN ]