Hacker News Reader

What interests me personally, also in light of this snarky comment here http://news.ycombinator.com/item?id=1924487 is whether Ruby 2.0 will do away with reopening classes and only allow the much better Refinements.

This will break most of the code out there, but in light of doing it cleanly, it would probably need to be done. On the other hand, a change like that will make sure that we might never see significant adoption of Ruby 2

View on HN

I don't think that editable classes and modules will go away, since they allow to spread the definition of a class to multiple file and/or serve as namespaces.

I don't know. I think it would be better to have ruby 1.8 and ruby 2.0 around and to state clearly that some code requires this or that version than having to deal with ruby 1.9 that is still close to 1.8 but not close enough not to break code.

Reply on news.ycombinator.com