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

Obie took the easy way and simply said 'oh it must be the crappy Twitter code'.

Too bad he is ignoring the very valid points about Ruby's slow runtime, memory usage because you are forced to a per-process mode, lack of proper threading and usage of dynamic languages in large systems.



A per-process model for Ruby doesn't have to use a fuckton of memory -- with fork() & COW, the processes could easily share.

Unfortunately Ruby has an awful mark-and-sweep garbage collector that writes to nearly every page on every collection, making COW useless.


This problem has been solved well over a year by Phusion Passenger (www.modrails.com) and Ruby Enterprise Edition (www.rubyenterpriseedition.com). It saves you tons of memory.


Forgive me as I'm unfamiliar with lower-level details like this, but isn't this exactly what Ruby Enterprise Edition is meant to solve?


'REE' - that is a joke right?


No it's not and it works quite well.




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

Search: