]> Shuttering… | CodeDread Blog

I want to believe. SVG as an image format.After finding some time to go through and mass-delete spam comments on this blog, I realized that it’s time to turn on the “Automatically close comments on post older than XX days” checkbox in WordPress. This means that posts older than 90 days will no longer be able to be commented on.

In case it’s not obvious, I haven’t been writing that much here these days. I’ve been too busy at my day job as a Google+ engineer and at my night job being a husband and father. If you really want to “follow me” these days, the best bet is Google+ for now. Let me know if you need an invite.

I’m not saying I won’t pick up the ol’ blogging pen from time to time. In fact, writing this very post has made me realize how much the UI has improved in WordPress. Also, I might have a couple new things to talk about in a little while, which I’ll likely post here and reference on Google+.

And yes, I’ve obviously been fully absorbed into the collective at this point :)

§1021 · September 11, 2011 · Uncategorized · · [Print]

3 Comments to “Shuttering…”

  1. As much as I dislike WordPress I still enjoy reading your posts here.

    I’m curious how SVG support in IE10 is coming along. The third preview build will be out September 13th with Microsoft’s Build conference.

    I’ve been thinking of a few ways to semi-automate checking test-cases you use to determine SVG compliance. I’ll send you an email in a bit with the details, I’d just need you to send me the list of links to the individual test cases you use.

    Also Presto and WebKit could both compete for 100% compliance on your test cases, they’re both rather close to it if one or both haven’t already achieved the feat.

  2. Damien says:

    Hello,
    I came across your blog after seeing it linked in the kthoom project, which I found when searching for js-unrar. I’m about to start a project that needs to unrar in the browser, but have opted to go the js-ctype route (and PPAPI with Chrome, eventually), as that would speed up development time (I think). It’s great to see that a JavaScript implementation is feasible. Seeing that HTML5 is the future development platform, I wonder how many decompression libraries will be officially ported to this platform.

  3. Hi Damien,

    It’s funny you should mention that, because I recently have started moving the code from kthoom that does the decompression over to a new project: http://bitjs.googlecode.com/

    This is one of the “new things to talk about” that I mention above :)

    The porting is not complete, because I wanted to update the software design such that it’s easier to make calls to the unarchiving code, but I just checked in the first revision last night that should include a working unzip implementation. The unrar and untar implementations still need a little work, but I should get that done by the end of the weekend, then I’ll probably make another blog post.

    Anyway, I always appreciate feedback, so please feel free to review the design docs and comment.