How to find memory leaks in your JavaScript code

tiljs.com

20 points·1p1e1··9 comments

Direct link: http://gent.ilcore.com/2011/08/finding-memory-leaks.html

From the whois and your tumblr, it looks like you (1p1e1) are the owner of tiljs.com. I have nothing against your site, but page from it aren't the correct type of submission to HN. Just give us a link to primary content you think we'll like to read and discuss.

Quite an investigation. ;) However, I believe a link to tiljs.com is more valuable than just the direct link of the article since tiljs contains not only 1 link but several (which can be found in the comments section).

That is the idea of tiljs - sharing several links and comments on a topic (in this case 'memory leaks in javascript').

Excuses if you found it irritating. Cheers.

Link to the source, not some crap re-tweet page. http://gent.ilcore.com/2011/08/finding-memory-leaks.html

There are some more useful links in the page I linked (you can find them in the comments section).

(http://ycombinator.com/newsguidelines.html)

> Please submit the original source. If a blog post reports on something they found on another site, submit the latter.

I know the guidelines. However, there is value added by linking to tiljs rather than only the direct link.

I'm curious why you thought a tweet was where you should link us.

It's not a tweet. ;) It's a website where people can post things they learned about JavaScript. So it doesn't only contain a link, but also additional comments with useful links, etc.

Reply on news.ycombinator.com