Thanks, Cedric, for insightful comments about documentation. I'll add that for me, if the only documentation is a video, I have to *really* want to learn about a programming tool to go any further. Videos don't allow you to take in information any faster than information at exactly the speed at which the video presents it. Reading lets you go faster, or slower, or visually decide what to skip, or find passages by their content. Even without hyperlinks. (Yes, when motion matters, video is nice.)
On Monday, November 11, 2013 12:04:09 AM UTC-6, Cedric Greevey wrote: > > IMO it can often be a lack of readable, searchable, nice-to-navigate > text/hypertext that can be a barrier to entry. In fact all of these are > unfortunately common in various parts of the geekosphere: > > 1. Projects whose *only* documentation (or the only version of certain key > information) is in videos. Not searchable. Not easy to navigate to a > particular part (need to remember roughly when it is, or rewatch half the > thing). Expensive for mobile users with capped or per-megabyte data plans. > -- -- 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/groups/opt_out.
