<div dir="ltr">As a Haskell novice I really appreciate the effort to put this together and look forward to seeing more of them. The video is high production quality and the pacing was fast enough that I didn't get too bored, even though I already had a pretty good understanding of the Haskell that was covered.<div>
<br></div><div>It might be worth saying in the metadata somewhere (title, description, whatever) that a lot of what is actually covered here is how Pandoc uses Parsec. I think that this content of this video would be helpful to anyone just starting out with Parsec, but they would probably only find it by accident as-is.<br>
<div><br></div><div>What I got most out of the video was just watching someone else's workflow. I think it would be helpful to some if you had some supplementary links in the description of the video that could help someone reproduce it locally. For example:</div>
<div><br></div><div style>- In the video it's not stated that "cabal install pandoc" (or equivalent) had already happened, and that this step is totally independent of the git clone.</div><div style>- A link to hasktags and perhaps even a link to documentation about Emacs TAGS might be helpful. I don't think this is a feature that all Emacs users are proficient with.</div>
<div style>- Having a PS1 prompt that contained the exit code from the last command was really clever, I hadn't seen that before. I'm sure some people would be interested in what the bashrc for that prompt looks like.</div>
<div style><br></div><div style>-bob</div></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Jan 7, 2013 at 3:50 PM, Chris Forno <span dir="ltr"><<a href="mailto:jekor@jekor.com" target="_blank">jekor@jekor.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I've just uploaded a video walking through<br>
some of the source code for Pandoc. I plan to<br>
create more videos like it (on Pandoc and other<br>
open source/free software projects), and I'd<br>
appreciate your feedback.<br>
<br>
<a href="https://www.youtube.com/watch" target="_blank">https://www.youtube.com/watch</a>?<br>
v=FEFETKhhq8w&feature=youtube_gdata_play<br>
er<br>
<br>
I think Haskell is particularly well-suited for this<br>
type of study:<br>
<br>
- The code tends to be concise, and parts can<br>
usually be analyzed in isolation thanks to<br>
explicit state.<br>
- Even after 10 years of exposure to Haskell I<br>
feel like I still have much to learn about<br>
idiomatic style from the writings of others.<br>
- I've run across the same misconceptions<br>
about Haskell in the professional world (and<br>
had some myself in the beginning), and would<br>
like more people to see what Haskell really is<br>
like outside of papers and blog posts.<br>
<br>
Please let me know if there are other projects<br>
you'd like to see me cover. Thanks.<br>
<br>
<br>
_______________________________________________<br>
Haskell mailing list<br>
<a href="mailto:Haskell@haskell.org">Haskell@haskell.org</a><br>
<a href="http://www.haskell.org/mailman/listinfo/haskell" target="_blank">http://www.haskell.org/mailman/listinfo/haskell</a><br>
</blockquote></div><br></div>