I believe this is the article (or part two of it): http://www.sitepoint.com/ruby-metaprogramming-part-ii/ Not only does Ruby do metaprogramming poorly, but Rubyists have managed to give it a bad name by too often…
In a persistent, image-based system where you can edit and debug programs in the very process in which they're running, metaprogramming is a necessity, not an anti-pattern. You couldn't implement Pharo's class browser,…
I believe this is the article (or part two of it): http://www.sitepoint.com/ruby-metaprogramming-part-ii/ Not only does Ruby do metaprogramming poorly, but Rubyists have managed to give it a bad name by too often…
In a persistent, image-based system where you can edit and debug programs in the very process in which they're running, metaprogramming is a necessity, not an anti-pattern. You couldn't implement Pharo's class browser,…