Re:The Dynamic Def – abusing Ruby's def statement
by TeMPOraL on Sunday October 18, 2015 @01:27PM
(#10408937)
Indeed. Looking over the article, the first example is sort of obvious if you ever worked more than few hours with a decent dynamically typed language, and the rest expose interesting functionality that could be papered over with a macro in order to build something useful. Like, you know, object-oriented programming can be built by hiding lexical closures under a macro or two, and was in fact built that way in the past.
In other words - just because you don't understand something doesn't mean it's "clever code".
In other words - just because you don't understand something doesn't mean it's "clever code".