This site will look much better in a browser that supports web standards, but is accessible to any browser or Internet device.
At the beginning of last year, I wrote Programming for/by Kids talking about my experience getting my young son programming using the Scratch language. Shortly after I wrote that piece, he lost interest and stopped. As usual, something else caught his attention and he was off working on that. When I noticed that he wasn't talking about wanting to program any more, I figured that he had worn out his desire to program and that would be it. I was a little disappointed, but he has his own interests.
Fast forward a little over a year and he is assigned a project in school to do a report on a book. From what he says, the teacher has suggested that the kids do PowerPoint presentations for their reports. (Fifth-graders doing PowerPoint, the world is changing...) My son decides that he wants to do something a bit more entertaining than a basic slide presentation. So, he fires up the Scratch environment and starts building a little movie for his report. He asked for a little help on a few things, but mostly works at it steadily for several days on his own.
As the project nears completion, we discussed the problem that his teacher might not be willing (or able) to install the Scratch environment to run his movie. With a moment's thought, he decides to get his digital camera and record a video of the movie playing on his screen. He put both the Scratch program and the video on a thumb drive and brought them to school. His report was a success.
Even though I had thought he lost all interest in programming, he had actually learned what he wanted and kept those skills for later use. Unlike this old programmer, he was interested in programming for the end product and not the process.
If any of you out there decide to try to teach programming to kids, you might want to watch for a completely different mindset than we had when we were learning. Given that computers are everywhere in kids lives today (their phones have more power than the first computers I programmed), they probably see programming very differently than we do.
At the end of 2008, I did a series of posts arguing that SVG still lives despite predictions of it's downfall. I had been hearing these dire predictions for years, and wanted to provide a decent rebuttal: Reports of SVG's death exaggerated.
Last year, I had the good fortune to go to SVG Open 2009. Despite following SVG for years and working with it where ever I could, I was still astounded at the creativity and power of the technology shown by many of the experts that were at the conference.
This year I had the opportunity to present at YAPC::NA on the topic Data Visualization with Perl and SVG. I expected a handful of attendees, and was surprised to be presenting to a packed room containing over 50 people. Apparently, there is quite a bit of interest in SVG.
There have also been a couple of changes in the world of SVG lately that should finally lay to rest the claims of SVG's demise.
* HTML 5 will include SVG support in-line with the HTML.
* IE 9 will finally begin supporting SVG natively.
As with many technologies, it looks like SVG has survived its first ten years and is about ready to break out into the mainstream.