"In explaining Clojure, for example, you'll find that the motivations are usually brought forth in a Rich Hickey talk. He talks about the motivations for immutable data structures, for time and state, for carrying metadata, and so much more. None of this is in the code base. "
I can sympathize with this point of view. I also think that Github wikis are a double-edged sword. They're convenient when you're exploring the repository in your browser, and a pain when you're not. It believe it would be a great first step to take the content from the Clojure website (where Rich has explained immutability, state, persistent data structures, etc) and store them as some variant of plain text (org mode?) in the repo itself. This is precisely the approach taken by git, for instance. In its Documentation folder you can find not only "man page" style docs, but also docs explaining data structures, motivations, things only contributors need to care about and so on. Tools can the process these files as well and make websites or wikis out of them. This is not quite the same as literate programming, obviously, but it seems to me to be an easily achievable first step for any project, including Clojure core, with potential benefits that surpass the effort required to make it happen. P.S. Sorry if the quoting is off...typing from a phone. -- -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to [email protected] Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to [email protected] 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 [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
