Source Maven

Code Partition for Beau Simensen

Embedding GitHub Gists

It is my opinion that embedding gists in a blog is a generally bad idea, unless you are writing on a site with terrible code support.

Last week GitHub released a pretty new version of Gist. Huzzah! Oh wait, it broke what now?


My first attempts at blogging about code involved WordPress. At the time there were a wide variety of source code formatters. I really didn't like many of them.

Posting Source Code with Wordpress is a pain in the ass. Is this really the way that the world handles dealing with source code in blogs? I know, not everyone in the world uses Wordpress. But a good chunk does. And Blogger's support for sourcecode was even worse.

I do not recall how long it took me to find Posterous but in playing around with it I discovered it had native support for GitHub Gist. Simply paste the Gist URL on its own line and BAM! instant code shared goodness in all its nicely styled glory.

I was hooked.

Not long after, I created what to this date might be my most used piece of software: the Embed GitHub Gist plugin for WordPress. Things were good. For a time.

After another year or so I grew weary of maintaining multiple WordPress installations and eventually moved my blogs to Posterous. It worked well in the beginning. Things were good again. For a time.

Eventually Posterous began to wear on me. It became slower. Its fancy publishing features worked only half the time. Its search was whack. I also started to subscribe to Dave Winer's opinions on Corporate Silos. I wanted to host my own content again but I didn't really want to worry about databases and keeping software up to date.

Around that time I was introduced to Jekyll. A little later I was introduced to Octopress. I was super excited to see that Octopress had a GitHub Gist plugin. It meant I could more or less continue to feed my blogging by Gist habit.

When I decided to roll my own static site generator (Sculpin) one of my big goals was to ensure that it would support plugins. The first plugin I wrote in order to prove my goal was a Twig extension (dflydev/github-gist-twig-extension) and a Symfony Bundle (dflydev/github-gist-twig-bundle). After all, if I ever wanted to host my coding blog with my own static site generator it better satisfy my Gist needs, right?


It took this new Gist update for me to really come to my senses. Long gone are the horrible WordPress days in which it was very difficult to properly embed code in a blog. Brandon is right. If your content platform can handle code natively and do a pretty decent job at it you should probably just use that.

Especially when taking into account the silo-free life I'd like my sites to lead it really makes a lot of sense to just write the code directly into my content. If I think it is important to share the code in a way that people can more easily collaborate I can simply link to a Gist.

Looking back I had already started to make this transition. About a month ago I finally got around to looking into highlight.js and integrated it into the Source Maven site. Since then I've only used simple Markdown code blocks for my source code sharing and things have been pretty nice.

I wish I could say my reasons were more forward looking. My main reason for making this change was not to rely less on Gist, it was because I was frustrated by needing to add <?php to the first line of my PHP source code for it to be properly highlighted by Gist.


When the full realization of the impact last week's changes would have on several days worth of my free time I became frustrated. I had built software on a premise that was starting to feel a lot more fragile than I had previously realized. I was receiving support requests for software I myself was no longer actually using. And to be quite honest, having to dive back into WordPress PHP did not help my overall attitude at all.

I did not see anyone else talking about the problems introduced by the new Gist until I saw this:

First, I wasn't alone! Second, I was pretty impressed that Brandon decided to take such a strong stance on the issue so quickly.

I've decided to take the same stance for Sculpin. Tonight I removed the GitHub Gist Twig Bundle from the Sculpin Blog Skeleton. I am no longer going to promote embedding GitHub Gists with Sculpin even if it is the best way to show a usable third-party plugin in action with Sculpin.


So where does that leave Embed GitHub Gist?

I have not often felt as helpless as I did realizing that countless sites relying on my software were either outright broken or looked absolutely horrible. To add insult to injury it was not my fault. Nothing changed in my software. I think that is the real problem here. People were relying on my software to share code from an entirely separate service. A service that nobody has any real control over.

I do not want to abandon the users of my most popular software but given there are hopefully better ways to handle this now (either by other WordPress plugins or moving off of WordPress if you are doing a developer blog) I do not think I will be devoting more resources to this project.

With the fixes from last week it should continue to work as-is until GitHub makes another breaking change. If someone feels the need to fork it and add additional functionality down the line I think I'm OK with that at this point. If the time comes to delete it from the WordPress plugin repository, I think it will be an easy decision.

As for me, I'm going to continue not using Gist to do any code examples that I plan to embed in blog posts.