Just 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.
Prismatic's "Graph" at Strange Loop
21–30 of 47 posts
Re: Prismatic's "Graph" at Strange Loop
#22If I understand the nature of this system, it's essentially a higher-order function composition tool. Correct? Nit, defnk? what about def-kw-func or something? not wholly readable as defnk.
Yep, that's correct. Point taken about the names, thanks for the feedback. Since Clojure already uses defn and fn, defnk and fnk seemed natural. But maybe defn-keyword and fn-keyword would be better.
I like to have fully expanded names, ala Common Lisp. My editor will autocomplete those on demand after I use a name once, so it's not a hindrance to reading or writing.
My goal for identifiers is that I can read without consulting my internal lookup table.
Re: Prismatic's "Graph" at Strange Loop
#23This 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 compon…
Re: Prismatic's "Graph" at Strange Loop
#24Re: Prismatic's "Graph" at Strange Loop
#25Earlier quoted context omitted.
Yep, that's correct. Point taken about the names, thanks for the feedback. Since Clojure already uses defn and fn, defnk and fnk seemed natural. But maybe defn-keyword and fn-keyword would be better.
I really like this idea. Do you have a Common Lisp port of this, out of curiosity? If not I might have to see what I can come up with. :-) I like to have fully expanded names, ala Common Lisp. My editor will autocomplete those on demand after I use a name once, so it's not a hindrance to reading or writing. My goal for identifiers is that I can read without consulting my internal lookup table.
Re: Prismatic's "Graph" at Strange Loop
#26This 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?
Here's a stupid simple js implementation of their example:
https://gist.github.com/3874826
Edit: Loaded the page and got interrupted by lunch. Shows me for not refreshing.
Re: Prismatic's "Graph" at Strange Loop
#27This 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?
You can do it in any language with first class functions and reflection. Here's a stupid simple js implementation of their example: https://gist.github.com/3874826 Edit: Loaded the page and got interrupted by lunch. Shows me for not refreshing.
Re: Prismatic's "Graph" at Strange Loop
#28Re: Prismatic's "Graph" at Strange Loop
#29Happy to see you're opensourcing. Are you planning to do the same with Flop and Optimize?
Re: Prismatic's "Graph" at Strange Loop
#30If I understand the nature of this system, it's essentially a higher-order function composition tool. Correct? Nit, defnk? what about def-kw-func or something? not wholly readable as defnk.
Yep, that's correct. Point taken about the names, thanks for the feedback. Since Clojure already uses defn and fn, defnk and fnk seemed natural. But maybe defn-keyword and fn-keyword would be better.