Although I didn't downvote you, you might have got your downvotes because your comment is irrelevant and not helpful.
Imagine someone struggling with tuning MySQL and someone else hijacking the thread with "MySQL is slow as molasses in January, use MongoDB/Cassandra/Distributed MapReduce in Erlang!". How does it help? If you want to discuss fundamental ruby issues like this one, submit your link separately.
> "MySQL is slow as molasses in January, use MongoDB/Cassandra/Distributed MapReduce in Erlang!". How does it help?
But that's entirely unlike what I wrote (although apparently that's how many people going through the thread read it). I was not advocating a different language/system whatever. I was pointing to an article saying "Existing Ruby implementations tend to randomly crash because of a very specific design flaw -- here's why that happens, and a possible, though not easy, way to determine if your crashes are a result of this design flaw". Given the info originally provided, it's hard to provide a more relevant link.
Personally, I don't care about Ruby, which is why I have no intention of submitting that link; and even if I did, based on the responses here, I suspect it would be downvoted as "badmouthing Ruby", rather than actually discussed. But I don't really care either way.
I was just surprised because while I have been downvoted before, it was never so harshly and without any discussion, especially since (if anyone actually followed the link they would have realized) it's possibly extremely relevant.
Imagine someone struggling with tuning MySQL and someone else hijacking the thread with "MySQL is slow as molasses in January, use MongoDB/Cassandra/Distributed MapReduce in Erlang!". How does it help? If you want to discuss fundamental ruby issues like this one, submit your link separately.