Open christopherreay opened 7 years ago
jsribosome.go interprets JavaScript zygosome.go interprets Lisp. I'm not really clear what ribosome.go does... maybe it's a generic model?
The nucleus.go is the container for all the ribosomes... and they basically end up processing actions which were in action.go (but Nico was suggesting some refactors to Eric... and I don't know where they stand in the refactoring process).
Ribosome defines abstraction of a code interpreter, nucleus contains the application parts, the DNA and actual instances of ribosomes that can run that DNA.
So this is the project: https://github.com/glycerine/zygomys/
We can look into seeing if it is reasonably debuggable
This changing of nucleus to ribosome happened in c64ff6fc as well as bd98af1 if you want to review the changes.
@zippy is that a human language semantic cohesion change or a change of underlying tool?
I wouldn't call it purely cosmetic as it's a refactor that tries to semantically better match the underlying metaphor. Before the nucleus was the application vm, and you could have multiple nucleii, and the Holochain structure held the DNA. Not the way cells work. Now the nucleus holds the DNA, the ribosome hold the VM that express the DNA. Much more accurate to the metaphor, if still not perfect. The Holochain object is now much cleaner and is about spinning up the whole system, nucleus, chain and dht.
But I also wouldn't call it changing the tool, more like reorganizing things into more logical places...
Talking about the GO tool which interprets javascript and lisp, etc...