|
|
|
|
|
by memling
1090 days ago
|
|
> But from a working-with-other people perspective, imagine opening some code and finding random invented constructs you have to reverse engineer and step through This feels just like working with another API to me. Macros can be arbitrarily complicated I suppose, but is the typical usage any more complex than learning an API? I don't really know, I guess, but my experience hasn't shown this to be that challenging. I can appreciate that programming languages are ultimately codifying a particular way to think about computation, and macros express more idiosyncratic ways of thinkingabout comouting that may not be readily understandable. I do think Racket has issues, but this isn't the first one I would cite. |
|