<3 HN
Haskell Live: A Live Coding Adventure
21–30 of 40 posts
Re: Haskell Live: A Live Coding Adventure
#22I have to say, I generally dislike video coding tutorials. First, it's difficult to google/copy-paste. Second, it just goes against the way I learn new programming languages - I generally read it, then try it, then experiment with it in some other ways, list few pages back/forth, experiment more, fail, then continue. Usually copypasting/rewriting chunks of code. "What happens when I do THAT? Oh, it fails miserably. W…
Re: Haskell Live: A Live Coding Adventure
#23I have to say, I generally dislike video coding tutorials. First, it's difficult to google/copy-paste. Second, it just goes against the way I learn new programming languages - I generally read it, then try it, then experiment with it in some other ways, list few pages back/forth, experiment more, fail, then continue. Usually copypasting/rewriting chunks of code. "What happens when I do THAT? Oh, it fails miserably. W…
"I can never actually learn any language from a video tutorial." I like video tutorials/screencasts as long as they have the following : 1. Trainer starts with a basic list of topics/table of contents. Nothing fancy but give me an overall overview of what I will learn out of this. 2. A particular topic is taught gradually i.e. by starting with a simpler or even wrong way (as in best practices) and then improving it t…
Re: Haskell Live: A Live Coding Adventure
#24This is awesome. Nice and approachable - well explained. I'd love if you also threw in some vim commands along the way.
I'd like to respectfully offer another opinion: I would NOT love if it some vim commands were thrown in. By all means, devote a single episode to tools, since the set up demonstrated might be complex to recreate, and it would likely be something a lot of people want to use too. But I don't think tips specific to a single editor have any place in screencasts that are about one programming language in general. An unobt…
My biggest focus in using vim was to get it out of the way so that I could focus on the Haskell. I wanted the environment (editor, compiler, window manager, test runner, etc) to be as transparent as possible. This is not, in point of fact, a series of vim tutorial videos.
I will make a video that explains my dev environment as a supplement, however.
I'd be happy to answer any vim questions in the comments (github issues, which I will hopefully figure out how to embed in the site eventually), and I do like the idea of adding call out boxes (no need to use subtitles, they can go on the video itself) to highlight interesting vim trickery.
Re: Haskell Live: A Live Coding Adventure
#25Earlier quoted context omitted.
I gathered the vim part. Is he pressing a separate key to run the stuff in the lower-right window or is there a vim hook to do that automatically?
For that I think he's using Guard ( https://github.com/guard/guard/ )
Left: vim with Vim Haskell Mode[1], a pale imitation of emacs haskell minor mode that nevertheless gets the job done. ;)
Top right: GHCi
Bottom right: Guard, as mentioned, using guard-shell[2] to compile the file and run main using runghci.
[1] https://github.com/lukerandall/haskellmode-vim [2] https://github.com/guard/guard-shell
Re: Haskell Live: A Live Coding Adventure
#26Earlier quoted context omitted.
For that I think he's using Guard ( https://github.com/guard/guard/ )
I'll make a video on my setup, but: Left: vim with Vim Haskell Mode[1], a pale imitation of emacs haskell minor mode that nevertheless gets the job done. ;) Top right: GHCi Bottom right: Guard, as mentioned, using guard-shell[2] to compile the file and run main using runghci. [1] https://github.com/lukerandall/haskellmode-vim [2] https://github.com/guard/guard-shell
Re: Haskell Live: A Live Coding Adventure
#27Earlier quoted context omitted.
Great suggestion, that's on par with what I had in mind. I was not implying OP should have a 3-minute segment on vim commands. Maybe just casually say "and I'm going to use :tab which allows me to select multiple lines and line up the equal signs" or something similar.
> Maybe just casually say "and I'm going to use :tab which allows me to select multiple lines and line up the equal signs" or something similar. No, I wouldn't want them to casually say anything... that's why the subtitles would be an unobtrusive compromise, since you can just turn them off. I think this would be even more important if the screencast was targeted at new users of the language or framework or whatever,…
Re: Haskell Live: A Live Coding Adventure
#28Earlier quoted context omitted.
I'll make a video on my setup, but: Left: vim with Vim Haskell Mode[1], a pale imitation of emacs haskell minor mode that nevertheless gets the job done. ;) Top right: GHCi Bottom right: Guard, as mentioned, using guard-shell[2] to compile the file and run main using runghci. [1] https://github.com/lukerandall/haskellmode-vim [2] https://github.com/guard/guard-shell
Maybe that info should be on the page itself somewhere. I wouldn't know to look at the github to find your guard script: https://github.com/haskelllive/haskelllive/blob/master/Guard...
Re: Haskell Live: A Live Coding Adventure
#29Earlier quoted context omitted.
> Maybe just casually say "and I'm going to use :tab which allows me to select multiple lines and line up the equal signs" or something similar. No, I wouldn't want them to casually say anything... that's why the subtitles would be an unobtrusive compromise, since you can just turn them off. I think this would be even more important if the screencast was targeted at new users of the language or framework or whatever,…
I want subtitles to perform their primary accessibility function. How about YouTube annotations?
Really nice video, looking forward to more!
Re: Haskell Live: A Live Coding Adventure
#30I have to say, I generally dislike video coding tutorials. First, it's difficult to google/copy-paste. Second, it just goes against the way I learn new programming languages - I generally read it, then try it, then experiment with it in some other ways, list few pages back/forth, experiment more, fail, then continue. Usually copypasting/rewriting chunks of code. "What happens when I do THAT? Oh, it fails miserably. W…