Hi Sebastian, Thanks for sharing! I'm enjoying read this document, and I plan to share it with a few teammates. I do have a question about one section however: Near the end, under "Principles and Community" you list three questions, and then state that if the answer to any of the questions is "No," that piece of software should be discarded. My question is about the second provided question, "Does it have many dependencies?" Wouldn't many dependencies be a bad thing? If the question (and expected answer) are correct, can you go into a bit more detail on why having many dependencies is a positive quality?
On Wednesday, August 12, 2015 at 11:52:39 AM UTC-7, Sebastian Bensusan wrote: > > Hi everybody! > > I've written a short post on my interpretation of Clojure. It is meant for > people that are curious about the language and want to understand what the > language is about. > > http://bensu.github.io/decomplecting_clojure/ > > Any feedback is welcome. > > Thanks to the folks at Slack that read the initial draft, specially Jeff > Kayser, Colin Fleming, and Viktor Eriksson. > > Best, > > Sebastian > -- 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.
