Lily
Start of topic | Skip to actions
Direct parentage, mostly the work of members of the RPI-ACM:
Cousins:
Offspring:
In addition to those listed above, the following projects, which I studied or worked on, had a significant influence on lily:
I don't recall ever refusing access to write a client for Phoenix, although no specific client-server protocol existed. I did refuse to allow anyone else to join me in server development; at the time, I wanted to retain complete control over the server and have it be 100% written by me. That's why it was a closed-source project. Eventually, I renamed the system to Gangplank and released the source code. It was probably a mistake not to open up the project more in the beginning, as Phoenix probably would have easily taken over from Clover if lily never existed. Oh well, hindsight is 20/20. As for Nexus, it is a long story indeed. The short version is that it was a joint project between Christian and myself, with GordonGoldberg? involved as a mediator and facilitator. The plan was to use the Phoenix source code as a robust foundation for a new CMC system, and basically reimplement lily on top of it, discarding the underlying MOO platform. We got far enough to choose a name (and "Nexus" is still my favorite CMC name to date), and for a while it seemed like the project would happen. Ultimately, the project fell apart due to disagreements over our respective roles in the project, despite Gordon's valiant efforts to keep it together. I suppose the project could be revived (anything's possible), but for now it's dead, and I guess it's all my fault.
-- DevenCorzine - 03 Nov 2003
While Nexus may be dead, there are a few (currently) independents working on reimplementing lily on top of something other than MOO, primarily to make it easier to do/coordinate server development. see the -lily3 discussion on RPI core. JoshWilmes?, JohnRedford? have both worked on implementations in other languages. Also, Rowboat (written by ThePrisoner) provides most of lily's functionality (though it is not a dropin replacmenet), implemented on top of Flow.
-- CoKe - 03 Nov 2003
to top
- CLoverUserEnvironment?: worked on
- EclipseParser?: studied
- TuringsTears?: designed, never implemented
- Eyes: studied
- Omni: worked on
- CloverSystemSummerProject?: designed, never implemented
- Phoenix (now Gangplank): refused access (had Deven allowed me to write a client for Phoenix lily would have never existed).
- Lily: a multiprotocol client
- lily: strictly for timing, this fits here
- Nexus: this is a long story if ever there was one.
- lilyCore: this goes here
I don't recall ever refusing access to write a client for Phoenix, although no specific client-server protocol existed. I did refuse to allow anyone else to join me in server development; at the time, I wanted to retain complete control over the server and have it be 100% written by me. That's why it was a closed-source project. Eventually, I renamed the system to Gangplank and released the source code. It was probably a mistake not to open up the project more in the beginning, as Phoenix probably would have easily taken over from Clover if lily never existed. Oh well, hindsight is 20/20. As for Nexus, it is a long story indeed. The short version is that it was a joint project between Christian and myself, with GordonGoldberg? involved as a mediator and facilitator. The plan was to use the Phoenix source code as a robust foundation for a new CMC system, and basically reimplement lily on top of it, discarding the underlying MOO platform. We got far enough to choose a name (and "Nexus" is still my favorite CMC name to date), and for a while it seemed like the project would happen. Ultimately, the project fell apart due to disagreements over our respective roles in the project, despite Gordon's valiant efforts to keep it together. I suppose the project could be revived (anything's possible), but for now it's dead, and I guess it's all my fault.
-- DevenCorzine - 03 Nov 2003
While Nexus may be dead, there are a few (currently) independents working on reimplementing lily on top of something other than MOO, primarily to make it easier to do/coordinate server development. see the -lily3 discussion on RPI core. JoshWilmes?, JohnRedford? have both worked on implementations in other languages. Also, Rowboat (written by ThePrisoner) provides most of lily's functionality (though it is not a dropin replacmenet), implemented on top of Flow.
-- CoKe - 03 Nov 2003
to top
Edit | Attach image or document | Printable version | Raw text | More topic actions
Revisions: | r1.8 | > | r1.7 | > | r1.6 | Total page history | Backlinks
Revisions: | r1.8 | > | r1.7 | > | r1.6 | Total page history | Backlinks