"Radian is currently proprietary. There are some contractual encumbrances that prevent us from open-sourcing it right now, but that may change at some point in the future."<p>So why would this be interesting for HN readers? The idea isn't that revolutionary, and there is no code and no way for people to do much.
This looks much more meaning fult than a div soup or even a proper table, I'd say. I'd definitely use it...<p>> There are some contractual encumbrances that prevent us from open-sourcing it right now, but that may change at some point in the future<p>...only if it were open source.
There is also Dangle (<a href="https://github.com/fullscale/dangle" rel="nofollow">https://github.com/fullscale/dangle</a>), which is D3+Angular backed by ElasticSearch. So, if Radian cannot be open sourced, perhaps Dangle can pick up the slack.
I've been building a lot of stuff with Angular and D3 lately, they make a good pair. The author has some good ideas here I'm looking forward to trying them out. The author may not be able to but I'll be perfectly happy to open source it.
Angular + d3 is beautiful. d3 is great but often far too low level and imperative (despite trying quite hard to be declarative). Wrapping d3 manipulations inside of Angular directives gives them a great deal of simplicity.<p>I find myself creating all kinds of different classes of graphs, parameterizing them on HTML attributes, and dropping them into Angular scopes. With a little bit of careful throttling and $applying you can even get highly interactive d3 graphs.