Speaking of memory leaks, I once had to debug a memory leak caused by console log entries. Objects that are logged to the console are prevented from being garbage collected, even if the console was never opened. That includes DOM nodes or I think also handles to WebGL textures.
Interesting, I think that's because logged objects are "live", so you can inspect their current state, not just the state at the point of logging.
That’s interesting. I’m guessing console.log appends to the window object somewhere, which is a fairly common method of image preloading.
Great thing!
Do you support rss feeds, so that I can stay up-to-date?
Each tip has a textual explanation, and an animated gif if you're a visual learner (I know, I need to scrap gifs and move to regular videos).
There's a lot of tricks there which can hopefully improve your development and debugging workflows. Let me know if there are specific things you'd like to see. A few people have asked for how to find memory leaks.