Re:Just what does “code as data” mean anyway? (2014)
by kamaal on Friday February 16, 2018 @01:39PM
(#16394659)
This looks more like software design problem and not a Lisp problem.
Building anything complex requires, apart from tools, getting organized in a lot of other things as well.
Re:Just what does “code as data” mean anyway? (2014)
by Retric on Friday February 16, 2018 @03:20PM
(#16395731)
That's part of it.
The is an old saying they enterprise software ends up mapping the organization that built it. If you have N teams you tend to break a large project into at least N parts.
Sharing code between teams works, but it's harder to share complex lisp macros vs functions. Which is really closer to my point, the larger the project the more tools get set aside too being to ~complex/risky to safely use.
Some of this comes down to what you consider a 'large' program. Suppose you want to build an MMO in lisp, now you need to consider things running on both a client, and server, as well as rendering, path-finding etc. Choosing reasonable primitives becomes difficult as you get pulled in several directions. Should I be running the same code on client an server or should I have multiple different models communicate etc etc.
My point is you start dealing with trade offs and no approach is universally better. Even with a clean API between different pieces of code you still get conceptual dependency's.