That is a very different implementation. It's a cool idea, taking advantage of the fact that gifs can be partially decoded, then generate the next frame on the

That is a very different implementation. It's a cool idea, taking advantage of the fact that gifs can be partially decoded, then generate the next frame on the fly and then send it over to the client as part of the same request (hello comet!), but there's a number of practical (to the extent that either of these are practical) differences. The svg can be downloaded, or cached, and it's functionality preserved (and can be viewed with a browser, even in offline mode). The gif solution technically would take an infinite amount of time to download. It requires an ongoing connection to the server, and it cannot be cached or distributed via a CDN. So, not the same thing at all, but very interesting.