Top all-time · #16574
David Glasser
Personal blog · point.davidglasser.netprogramming
David Glasser writes floating point, a personal blog at point.davidglasser.net about programming. Since 2013, 4 different Hacker News readers have linked it 6 times, most often “A surprising JavaScript memory leak found at Meteor”. The last post was in 2013, but the archive is still widely read.
Too few sampled comments (5) to say how often HN recommends it.?
Why HN links it
A personal blog on JavaScript, with a 2013 post on surprising garbage collection and memory behaviour. HN commenters cite it when discussing JS memory leaks and embedding JS versus Lua.
Summarised by Claude from a sample of 5 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.
Most-linked posts?
- A surprising JavaScript memory leak found at Meteor4 people · 6 mentions · first linked 2013-06-28
What Hacker News says?
>> No pointers, no memory allocation. There are definitely both of those things, they just aren't explicit in the same way.[1] [1]: http://point.davidglasser.net/2013/06/27/surprising-javascri...
Comment linking /2013/06/27/surprising-javascript-memory-leak.html
on “Enough with the JavaScript already”Submitted A surprising JavaScript memory leak found at Meteor as a story · 179 points
HN discussionFWIW there's still a pretty large delta from Lua and JS as far as embedding targets go. We use to run our whole game state in a 800kB fixed block on a 8mb system heap in vanilla Lua(pre-LuaJIT) with good success. I've done some poking at various embedded JS frameworks like Duktape and it's pretty easy to trip on various memory leaks[1] that make it really hard to recommend it as a viable platform for memory constrai…
Comment linking /2013/06/27/surprising-javascript-memory-leak.html
on “Gravity – An embeddable programming language”They mentioned memory leaks as their reasoning. Run the following program in any browser and you will see the memory usage balloon out of control: var theThing = null; function replaceThing(){ var oldThing = theThing; function unused(){ return oldThing } theThing = { longStr: new Array(1000000).join('*'), someMethod: function(){ } }; } setInterval(replaceThing, 1000); V8 (and all other engines I tested) will save th…
Comment linking /2013/06/27/surprising-javascript-memory-leak.html
on “Node.js Best Practices”v8 (and all other JS engines I tested) are kind of stupid when it comes to garbage collection. You can see a detailed explanation of the problem in this blog post: http://point.davidglasser.net/2013/06/27/surprising-javascri...
Comment linking /2013/06/27/surprising-javascript-memory-leak.html
on “Node.js Best Practices”> Lua is semantically almost identical to modern JavaScript. Having spent a lot of time looking pretty hard at Lua, LuaJIT, and embeddedable variants of JS(duktape and the like) I think that's a bit of a stretch. It's pretty trivial to induce JS memory leaks[1] that can be brutal on embedded platforms. We had a prototype project written in JS and Lua, same functionality but hit issues like this pretty often. Like mo…
Comment linking /2013/06/27/surprising-javascript-memory-leak.html
on “Tables”