Hi John, nice post, and enlightening. I should note that I've been contemplating creating a framework for playing with graphics and maybe random text on the screen (think BASIC's "LOCATE" and "COLOR") intended for children, teenagers and other people who like to see results. I recently found something interesting like that done in Racket http://docs.racket-lang.org/quick/ - see its tutorial .). Maybe it can be done inside the web-browser too using Perlito (a Perl 5/Perl 6 to themselves and to JS compiler) or https://github.com/kripken/emscripten (which converts LLVM bitcode to JS). Also please consider recommending http://perl-begin.org/ as well as http://learn.perl.org/ , because it is more comprehensive and may be suitable for different kinds of people. Its navigation menu may be a little daunting for some people, but I feel its various resources, fill many useful niches, and it is under active development and open content/free content (mostly CC-by). Someone told me he is looking for a more “hands-on” tutorial (said in English inside a Hebrew sentence) on Perl, but I need to think about it. Maybe an interactive REPL. Good luck.

Hi Wil! I found this post of yours touching and inspiring. As opposed to you, I'm making all my works of art available under freely-distributable licences (including Public Domain, MIT-X11-Licence, CC-by, CC-by-sa, etc.) so people can share them, re-use them, cite/quote them, build upon them and enjoy them. In short - to enrich the commons. Of course, I didn't really try to make a living out of them yet. See what I wrote about it for more information: * http://www.shlomifish.org/philosophy/case-for-file-swapping/ * http://www.shlomifish.org/philosophy/philosophy/closed-books-are-so-19th-century/

Hi Wil! I found this post of yours touching and inspiring. As opposed to you, I'm making all my works of art available under freely-distributable licences (including Public Domain, MIT-X11-Licence, CC-by, CC-by-sa, etc.) so people can share them, re-use them, cite/quote them, build upon them and enjoy them. In short - to enrich the commons. Of course, I didn't really try to make a living out of them yet. See what I wrote about it for more information: * http://www.shlomifish.org/philosophy/case-for-file-swapping/ * http://www.shlomifish.org/philosophy/philosophy/closed-books-are-so-19th-century/

Hi! I'm sorry that I have to comment on your blog post, but I have no choice because the email address on: http://search.cpan.org/~btrott/ Bounced from gmail, and I could not find your newest one online (including not on this site). Please update your CPAN email address. I wanted to send you this: {{{{{{{{{{{{ Hi Mr. Trott! I started to enhance and fix bugs and limitations with XML-Feed here: https://svn.berlios.de/svnroot/repos/web-cpan/XML-Feed/ I'd like to upload my enhancements to the CPAN and to also be able to close bugs, so I'm requesting you for a co-maintainer status. This is my CPAN author page: http://search.cpan.org/~shlomif/ I already have become a co-maintainer of Error.pm, XML-RSS, and XML-SemanticDiff, and naturally initiated many modules of my own. Regards, Shlomi Fish }}}}}}}}}}}}

Thanks for the great post! I greatly enjoyed it. I can relate to the post getting lost. What I normally do to prevent is write all of my posts in a text file using a text editor (I'm using gvim, but there are plenty of other very good FOSS and non-FOSS ones), and then copy and paste it to the blog's edit box before posting. This way, I also keep a backup of everything I've ever written. Software is unreliable and web-based-software doubly so. I also encountered a worse phenomenon when sometimes WordPress blogs ate the comments I posted and wouldn't let me re-post them claiming they were identical. And the blog owners did not know what to do because they weren't WordPress experts. They also held the WordPress version back, which probably exposed them to many security vulnerabilities. I hate WordPress. Regards, Shlomi Fish My homepage: http://www.shlomifish.org/

Thanks for the great post! I greatly enjoyed it. I can relate to the post getting lost. What I normally do to prevent is write all of my posts in a text file using a text editor (I'm using gvim, but there are plenty of other very good FOSS and non-FOSS ones), and then copy and paste it to the blog's edit box before posting. This way, I also keep a backup of everything I've ever written. Software is unreliable and web-based-software doubly so. I also encountered a worse phenomenon when sometimes WordPress blogs ate the comments I posted and wouldn't let me re-post them claiming they were identical. And the blog owners did not know what to do because they weren't WordPress experts. They also held the WordPress version back, which probably exposed them to many security vulnerabilities. I hate WordPress. Regards, Shlomi Fish My homepage: http://www.shlomifish.org/