Since we're on the topic of forking...
About a year and a half ago, I basically took maru-2.1 apart and rebuilt it
from scratch as a learning experiment. Also, in the spirit of fonc and the
sciences of the artificial, I wanted to write experiments against the maru
system - these of course boil down to expressing a new system / language IN
maru (I've called those sets of experiments / language / system "modernity")
Given the recent interest in trying to understand maru, I figure I'd share my
heavily documented experience doing this.
https://github.com/strangemonad/modernity
In many ways this was an adventure in software forensics and trying to put
myself in Ian's mind / frame of thinking.
> (That's a personal gripe and might be blowing my dislike of github, et al.,
> out of all proportion. :)
Or maybe a gripe against the way the Linux kernel devs organize their work?
>
>> Here is how I would imagine my dream world. It would be a central
>> repository with:
>>
>> - A toy Maru, optimised for clarity.
Hopefully, what' you'll find in modernity/tools fits this. Let me know if it
doesn't
>> - A tutorial for writing your own toy.
That is basically the intent with the modernity system in modernity/src. You'll
see a few references to "books". My hope is to have a rich enough gui to load
an active-essay that is the description of the system. Similar to the
Physically based ray tracing book (http://www.pbrt.org/).
>> - The hand-written bootstrap compilers (for understanding, and the
>> Trusting Trust problem).
see modernity/tools/maru-bootstrap (for the C version) and modernity/tools/maru
for the maru-in-maru implementation
I'd be curious to see what parts are more understandable and what parts are
still confusing to folks. Since I spent a good 4-5 months steeped in this much
of this makes a lot of sense to me but I'm sure there's still lots in the way
of handholding for a newcomer.
shawn
_______________________________________________
fonc mailing list
[email protected]
http://vpri.org/mailman/listinfo/fonc
