Carl Mäsak

Much of the thinking-out-loud in this issue is about looking ahead, and trying to arrive at a module/imports system with, let's say, nice scalability properties. The simplest possible version was...

Back when I was thinking about "**pods**" — which I fear I might not have written down anywhere in this repo — I had a few more requirements. Briefly, pods...

The README.md mentions using `(bootstrap)` to mark the place where you want to use the evaluator _in the current globals_ as your evaluator. It would be possible to do your...

> A "replace" is similar to a delete; it's a reified deliberate change of something that existed before. Even here, there would be corner cases to consider. I also realize...

> Briefly, pods would be module-like, yes, but primarily they would be independent processes, more like software components or actors. The axis of composition would still be imports/exports, but with...

Just doing some drive-by-commenting here: Bel is fundamentally a very interpreted/dynamic language, and modules are a feature that reaches towards the compiled/static end of things. Not that they clash, as...

> The README.md mentions using `(bootstrap)` to mark the place where you want to use the evaluator _in the current globals_ as your evaluator. It would be possible to do...

> Briefly, pods would be module-like, yes, but primarily they would be independent processes, more like software components or actors. The axis of composition would still be imports/exports, but with...

Not to mention being able to change the code itself! Consider [the change I needed to make here](https://github.com/masak/taocp/pull/21/commits/97745f46cc957f27445975392fcc499d1e2bec04) to (the call to) the `make` macro. I don't remember exactly how...

> (I don't remember where I read or heard the phrase "communicating with aliens"; probably somewhere in the vicinity of Kay. [...]) Ah, I remember now. I heard it in...