Vassil Nikolov<p>[AMOP]<br><span class="h-card" translate="no"><a href="https://mathstodon.xyz/@dougmerritt" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>dougmerritt</span></a></span> <span class="h-card" translate="no"><a href="https://mathstodon.xyz/@weekend_editor" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>weekend_editor</span></a></span> <span class="h-card" translate="no"><a href="https://universeodon.com/@sigue" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>sigue</span></a></span> <span class="h-card" translate="no"><a href="https://mathstodon.xyz/@abuseofnotation" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>abuseofnotation</span></a></span> <span class="h-card" translate="no"><a href="https://gamerplus.org/@screwlisp" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>screwlisp</span></a></span></p><p>Right now I'm thinking that the real value of _The Art of the Metaobject Protocol_ is showing one way to do metaprogramming, and object-oriented programming is merely a demonstration domain.</p><p>Of course, what begat AMOP was a desire for an approach that can cover a large part of the OOP language design space, not just one point in that space, in order to be attractive to different schools of thought.</p><p><a href="https://ieji.de/tags/AMOP" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>AMOP</span></a><br><a href="https://ieji.de/tags/CLOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CLOS</span></a><br><a href="https://ieji.de/tags/CommonLisp" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CommonLisp</span></a></p>