Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

The standard Ruby interpreter never releases memory to system once it allocates it. Ever. This is expected behavior.

One of the founders of Twitter mentioned seeing an Engine Yard guy copy a 500 meg file from one machine to another. That instance of the interpreter allocated 500 megs and wouldn't let it go till it is killed.

All this is the result of Ruby having to support Eval().

I love Ruby. I don't program in it anymore and I think that's tragic. I can see how Lisp is great just in the since that in a homoiconic language, eval is OK.

But Ruby is nice and so much more intuitive, productive and beautiful and welcoming than those homoiconic langs.

Perhaps this is why _why vanished... The Marcel Proust of the 21st century needs to write a tragic .... user's manual on the subject.



Sorry, maybe i'm just not thinking clearly this late at night. Why in the world is supporting eval related to hanging on to 500 megs of unused memory?

Ruby is neat and all, but is there really anything in ruby that's not dressed up smalltalk? Squeak doesn't randomly hang on to 500m, afaik.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: