On Aug 19, 2014, at 19:52 , Marvin Humphrey <[email protected]> wrote:
> Clownfish is likely to remain in significant flux at least until we've > implemented bindings for more languages. Here are some of the upcoming > challenges which will likely require modifications to the Clownfish core: > > * Tracing GC (Ruby, Go) I’ve also been thinking about this. It should be feasible if we keep track of all Clownfish objects that were passed to the host language. > * Non-UTF-8 host string type (Python) A simple approach would be to reencode every string that is passed from the host language and back. But for a more performant solution, Clownfish needs support for multiple string encodings. > * Limited access to GC internals hampers host subclassing (Go) I don’t know anything about how Go interfaces with C, but I can imagine that the lack of virtual methods in Go poses an interesting problem. > This is super fun stuff to work on. :) I hope you didn’t mean that ironically. It definitely sounds like fun stuff to me. :) > Having Lucy as a real-world example is invaluable during this period and I > think releases will be coordinated for a while yet. Yes, but now that Clownfish is cleanly separated, it should be much easier to start supporting new host languages without having to care about Lucy at first. Nick
