Christian, as for historical reasons David used Coco. It's honestly mostly because it's a better more productive language and partly because David is a hardcore aesthete who seriously dislikes meaningless characters like brackets, etc.
Ori, I think your point about Limn not being the answer forever is great. We really do need to talk about what we want out of visualization and why we can't use the many, increasingly sophisticated frameworks being developed. Like pure D3 with a few templates or plugins via Rickshaw, Vega, etc. But, as to what's valuable in the non-library 250k or so of Limn code. The purpose of Limn was to make it fun to play with data in real time. We had to stop working on Limn before we could show progress towards that goal. The one unique thing in that 250k is the marriage of D3 with Knockout. This establishes a novel way of writing visualization components that are compatible with the end goal by design, out of the box. In other words, we now have only to write the UI via which people would actually play with the data. We know of no other work in this space and it's very exciting. It's the kind of stuff that Brett Victor was playing with in Tangle JS, and we would really further that kind of deep, intuitive understanding of data if we went forward.
Analytics mailing list