Looking at the Event stream, I thought it would be interesting to visualise what was going on in live, in a web browser, and given all the toys I've written over the past year or so in NodeJS, it was fairly clear that a simple web server processing the events and broadcasting them to clients wouldn't take a lot of work to complete.
So, we ended up with Github Live, which looks something like this once you've left it running for five minutes (during the morning, so it's a bit quiet)
The server side
The server is using Node, which is operating as a basic static file server, and as a point of call for incoming sockets with socket.io.
It starts off every 10 seconds polling the Events API, storing the most recent timestamp so to avoid publishing duplicates (the events API doesn't have a "last retrieved id").
It attempts to throttle requests to the events API to avoid the amount of duplicate events being retrieved from the API (if it finds an overlap, it increases the time until next request by a second, and if it doesn't, it decreases by a second).
In hindsight, the hideous inline callbacks would be best replaced with a stream that did all this work, and just published events transparently to the consuming code.
The next job, once this has taken place is that a request is made to Github for each pull, asking for information about the repository (for the language), so the events being streamed to the clients can be augmented with this information.
This is another thing that should be dealt with by a stream rather than inline callback soup.
Oh well, it's only 200 lines of throwaway code, perhaps something to tidy up on a rainy day.
The client side
Because it's quick and easy, we're using HTML and CSS3 to do display and transformations.
As the events stream in from the server, some HTML is created for the event and it is put in an appropriate bucket (for the language being used).
The outside container has a CSS transition applied to it, and the transform 'scale' is set to fit all buckets into the same window periodically.
From this I have ascertained that
I guess with some more work, these things could be worked around, there are some definite performance improvements that could be made client side here.
I'd quite like to give an SVG implementation a go, and see about the performance of that. Another project for a rainy weekend.
The code in all its (raw) form can be found at https://github.com/robashton/githubfall
I'd be interested to see any obvious improvements made and pull requested in.