From: Zeno Davatz Date: 2011-01-21T21:57:31+09:00 Subject: [ruby-core:34735] [Ruby 1.8-Feature#4239] Let's begin a talk for "1.8.8" -- How's needed for surviving 1.8? Issue #4239 has been updated by Zeno Davatz. Dear Bill In my opinion you prove to like theory over practice. Ok, the Hash-Iteration happens with big Hashes, surely so, but please show me one _practical_ Use-case where i.e. the Users of Ruby 1.8.6 like Engine Yard complain that it is a problem for them? This whole thing is based on to many ifs and whens and one maybe! You still have not shown me a real-life practical use-case. Also in your first code example where is your Hash? I get No2 and No3, No3 has a long Hash and that creates an error. But I do not know of a practical use-case for that. In contrast I have a very simple Use-Case for you. Ruby 1.9.2 breaks the dbi gem because the dbi-gem uses simple normal HashIteration to load Data from our Postgresql 8.4 database into the Cache in our application. We have millions of Views per Year (peak time can be 2000 - 3000 rps) and not a single complaint with Ruby 1.8.6. But if we want to switch to Ruby 1.9.2 then it just stops working because the dbi-gem does not work anymore and that thing has a huge tail! And this is what Ruby should care about. This is what Linux cares about but I think you do not really notice that. So this my practical proof for you. So ask yourself: What is more important: The normal practical use-case or the scientific one? Of course it is the normal practical use case. Ruby should not care about the long Hash-Iteration-Problem so long as there is no practical use-case. Engine Yard and all the other Ruby 1.8.6 users seems to work perfectly fine with normal HashIteration. Best Zeno ---------------------------------------- http://redmine.ruby-lang.org/issues/show/4239 ---------------------------------------- http://redmine.ruby-lang.org