Prismatic's "Graph" at Strange Loop
blog.getprismatic.com
Prismatic's "Graph" at Strange Loop
1–10 of 47 posts
Re: Prismatic's "Graph" at Strange Loop
#2Very interesting, needs more examples though.
It seems like this fits a similar purpose to Nathan Marz' Storm framework. Could you do a bit of a compare/contrast thing between Graph and Storm?
Re: Prismatic's "Graph" at Strange Loop
#3Nice. Assuming that the computation of each node is memoized, can we 'dirty' a single node, so that during the next computation only the needed parts of the graph are recomputed? This would make multiple computation of models where only a few parameters are changing much more efficient.
Also, has this at all been inspired by SecDB's powerful graph oriented features?
Re: Prismatic's "Graph" at Strange Loop
#4This sounds very useful. I'm having trouble understanding the nature of the system, though, because I don't really understand lisp / clojure. Is this a pattern that could be applied in any language with first class functions, or does it require a lisp to be practical?
Re: Prismatic's "Graph" at Strange Loop
#5[deleted]
Re: Prismatic's "Graph" at Strange Loop
#6Just a heads up, it looks like something is up with your CSS:
http://cl.ly/image/241X1C2D3O35
I'm on 10.8 with the latest version of safari.
In other news, this looks pretty cool.
Re: Prismatic's "Graph" at Strange Loop
#7Just a heads up, it looks like something is up with your CSS: http://cl.ly/image/241X1C2D3O35 I'm on 10.8 with the latest version of safari. In other news, this looks pretty cool.
Are you using a Retina Macbook?
Re: Prismatic's "Graph" at Strange Loop
#8This sounds very useful. I'm having trouble understanding the nature of the system, though, because I don't really understand lisp / clojure. Is this a pattern that could be applied in any language with first class functions, or does it require a lisp to be practical?
Sure! This particular way of expressing declarative structure may be specific to Clojure, but the basic ideas should be useful in any (especially dynamic) language with first-class functions.
The first idea is to take a complex system and express the set of components and their relationships declaratively, rather than procedurally. This is an old idea, and makes it possible to reason about the system, mock out components for testing, map over the components for monitoring, and more.
The second idea is simplicity. By making this declarative language as simple as possible, it becomes trivially easy to do all the things I just mentioned using the existing tools in the language, without needing to write complex library functions to support each use case.
For another example of a declarative system for composition you could look at 'react' in JS, which can be used in similar ways to Graph (and also supports things like async composition): https://github.com/jeffbski/react