Hi Nahuel, I think from a technical perspective something like Datomic would be a good fit, I think it has the right ingredients. If Git allows access to the lower layers, that may also be a good fit. One of my frustrations with source control systems is the way you end up repeating information, e.g. Modified function X, Refactored function Y. Added defmethod etc… This information is already present in the commit, after all its what you DID. The system should be able to work that out and provide that information. Granted source control systems don't do this today because they have no semantic understanding of the code, its just text to them. Wouldn't it be nice if the commit automatically compiled a list of the changes, E.g. the functions added, parameters added, functions removed, refactored etc. My belief this that a user provided commit statement should contain the WHY not the WHAT. The system can determine the WHAT but not the WHY. If the information generated by the commit was structured in some way useful queries could be run against the source control system. E.g. show me the commit which added parameter "foo" to function "bar".
On 18 Jul 2012, at 13:46, Nahuel Greco wrote: > What about storing the vars definitions in Datomic? Maybe augmented > with semantic information ("added defmethod", "redefined function", > etc). > > Saludos, > Nahuel Greco. > > > On Wed, Jul 18, 2012 at 5:19 AM, Mark Derricutt <m...@talios.com> wrote: >> On 17/07/12 10:27 PM, N8Dawgrr wrote: >> >> >> In a nutshell its about why use files for source in Clojure, can we do >> better? >> >> Almost sounds like you're wanting the Smalltalk "image" along with something >> like Monticello - the smalltalk distributed version control system ( >> versioning at the function layer would be awesome ). >> >> http://wiresong.ca/monticello/ >> >> >> -- >> 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 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 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