Re:Tracking down a memory leak in Ruby's EventMachine
by pc on Thursday March 07, 2013 @01:01PM
(#5339067)
I wish there were more posts like this.
[ Parent
| on HN ]
Re:Tracking down a memory leak in Ruby's EventMachine
by Legion on Thursday March 07, 2013 @01:40PM
(#5339308)
This is what I think of as the ideal HN - posts that are "How I Made X" or "How I Debugged Y" (or even "How Someone Else Made X", like the Amazon menu post, though the author ended up making their own implementation too).
No product announcement links, no Valley gossip rag links, no endless picking apart of every tiny Apple and Google thing.
What makes HN special are posts about making things. Everything else is just the same chatter all the other tech sites have.
Re:Tracking down a memory leak in Ruby's EventMachine
by gruseom on Thursday March 07, 2013 @01:42PM
(#5339320)
Me too. I wonder what would make for more posts like this.
Re:Tracking down a memory leak in Ruby's EventMachine
by grey-area on Thursday March 07, 2013 @04:05PM
(#5340240)
Go here every day and upvote interesting articles after reading them.
Re:Tracking down a memory leak in Ruby's EventMachine
by gruseom on Thursday March 07, 2013 @04:09PM
(#5340269)
No, what I'm saying (cf my other comment in this thread) is that it's actually a supply problem.
Re:Tracking down a memory leak in Ruby's EventMachine
by grey-area on Thursday March 07, 2013 @04:33PM
(#5340427)
Not sure I agree there. There are lots of interesting posts which sink on that queue and fall off it without getting sufficient votes to be seen, while less interesting but more controversial stuff floats to the top. All it would take is a few score more people voting technical stories up consistently to change the story mix.