I'm not sure hygienic macros are gonna be that much of a top-seller in user code, I agree. But there are situations where it would be very handy, especially as

I'm not sure hygienic macros are gonna be that much of a top-seller in user code, I agree. But there are situations where it would be very handy, especially as library developer. Macros would for example make optimized code generation a lot nicer. I feel it's the same with the work towards a core MOP. It will be hard to convince regular users why the new thing is better, but for people writing extension, auto-documentation tools, or other introspective systems it'd be a huge relief (at least to me). The difference I see is that instead of extending OO in the sense of a framework on top (Object::Tiny, Class::Accessor), you compose in behavioral extensions.