Re:Codeq
by jcromartie on Wednesday October 10, 2012 @12:00PM
(#4636885)
I think that Lisp actually strikes a great balance here. The data structures that represent programs are simple and unambiguous, and they serialize to text files absolutely trivially. We should be able to work with code-as-data while making use of text-based persistence and versioning.
[ Parent
| on HN ]
Maybe if someone invented a "new" programming language where programs were valid JSON, without mentioning the obvious connection to Lisp, programmers could be tricked into using it.
Programmers seem to love adopting the features of Lisp, as long as they can re-assure themselves they are not actually programming in Lisp.
Re:Codeq
by tomjakubowski on Thursday October 11, 2012 @12:08AM
(#4639334)
Srikumar K.S's jexpr is an experimental (and it seems abandoned) attempt at doing just this:
http://srikumarks.github.com/jexpr/
{do: [
{fetchURL: "http://some.data.source/",
timeout: 30.0,
onfail: {raiseError: "URL not reachable"}},
{fork: [
{displayInElement: "element_id"},
{cacheInLocalStorage: "prefix"}
]}]}
more here:http://srikumarks.github.com/gyan/2012/04/15/j-expressions/
http://srikumarks.github.com/gyan/2012/04/14/creating-dsls-i...
Re:Codeq
by darkxanthos on Thursday October 11, 2012 @08:37AM
(#4640514)
Wow this is pretty great! Never knew about this and might play with it some. Thanks!
MISC might be of relevance here:
http://lambda-the-ultimate.org/node/2887
EDIT: And for the record, I actually think it's a brilliant idea.