I really like the idea of using GitHub as a form of blogging about code, after all what better way to distribute code and small pieces of text describing it than a DVCS. I think I'll start doing the same with the code related posts on my blog.
" ... after all what better way to distribute code and small pieces of text describing it than a DVCS. "
Not that what Reg is doing isn't interesting, but what does a DVCS blog buy the reader? Will I be doing a local pull from someone else when github is down (or when he just doesn't feel like writing :) )?
On the other hand, the blog doesn't have support for comments, so I thought about forking the repo, adding my own comment to the text, then sending back a pull request. Presto.
I don't know about the D part, but there are some advantages to a CVS. For example, if you cared to you could get everything for reading offline at your leisure.
And while it seems cumbersome for words, it is more convenient than a blog for code that I post. In the past I put some code up on web pages, some on FTP, and some on rubyforge, all linked from my blog. Now all the code you might want to download is in one unified repository.
This is an experiment, so we'll see how it goes. But I'm hoping that it will be a win for things that are code-y rather than wordy.
> On the other hand, the blog doesn't have support for comments, so I thought about forking the repo, adding my own comment to the text, then sending back a pull request. Presto.
Issue with that is no fulltext posts. Of course you can always hack together a Y! pipe that takes the post body HTML and adds it to the feed, but that seems like a lot of hackery just to get an RSS feed going.
