As Stuart Halloway points out, "all code is data, but all data is not 
code". That said, I'd like to see spec lean as far as possible in the 
direction of simply being based on data structures. By way of motivation, 
let's suppose that I have a Sinatra (Ruby) server that is communicating 
with Elm or JS client-side code and/or a Clojure or Elixir back end. If I 
could define specs in a cross-platform manner, I could use the same specs 
to define messages throughout the system. FWIW, my preference would be to 
use transit.js to facilitate transfer of higher-level data structures among 
the components.

-r

-- 
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to