vyzo

I would also like to add that Scheme|Gerbil is not so brittle with regards to interface changes, because there are no type signatures -- just functions (and macros). So as...

Another point that is not salient here, is that Gerbil's explicit control of the namespace (with the namespace and package declarations, together with gerbil.pkg hierarchies) allows both new and old...

Note that namespaces can be populated by multiple independent packages. So you made a new shiny interface for your library and don't want to keep around the old one? Fork...

To finalize my tirade: I am philosophically opposed to polluting programming with versioning cognitive burden. The module system should let you control your namespace and your library structure so that...

In real life, there is no program of sufficient complexity that is actually correct, no matter what versions you choose -- all real programs have bugs, inconsistencies, and what have...

> I'm not just talking about "sufficiently complex" programs or the existence of bugs... a 10 line program that imports an unversioned feeley/digest will no longer work if that module...

Also lest we forget: i neglected to mention the word "state" in the mobile code stuffs, but it is the actual hard problem in recovering mobile code environment necessary to...

Not to mention that current best practice for what passes for mobile code in the wild (eg js, java) is to either use source, or bytecode (webassembly, java class files)....

that sounds fine for prototype purposes.

Also created a repo for the pure gerbil implementation: https://github.com/vyzo/gxpkg-daemon