Re:Say “no” to import side‐effects in Python
by einhverfr on Saturday April 05, 2014 @12:45PM
(#7537556)
In Perl, I find metaprogramming to be extremely powerful. I don't go too deep into Class::MOP usually. However, I do find that focusing on tooling before code is usually a net win. This means a lot of work can be done by writing DSL's that use metaprogramming behind the scenes. It works well and has become a common approach for certain kind of things (like object frameworks).
[ Parent
| on HN ]
Re:Say “no” to import side‐effects in Python
by mercurial on Sunday April 06, 2014 @02:10PM
(#7541864)
I'm not saying you should never use metaprogramming. Sometimes there is no other (practical) way. But it can be easily abused, often for a little added convenience but a much larger conceptual complexity and additional debugging issues. Why have a well-designed API when you can have a metaprogrammmed mess instead?