Archive for the 'Uncategorized' Category

March, a month in review.

March 29, 2011

I’ve tried not to do too many “life-update” type blog posts on this blog thus far, instead focusing on analysis of things that other people are doing, but a lot of stuff happened to me this month, so I’m just gonna roll with it. Everything is divided into sections. There’s still some music stuff here. Just skip over the things you don’t care about. Click through to read the rest!

Read the rest of this entry »

March Madness Quadruple Bracket

March 17, 2011

So, I filled out 4 brackets this year (more on that later). I like having my brackets with me on paper form, but don’t like carrying around 4 sheets of paper. Here’s the solution I came up with:

(click the image to bring up a full-sized version which you can print out. you’ll probably have to click “scale to page”)

Preview: The Mountain Goats, All Eternals Deck

March 2, 2011

I’m not ready to review this yet, but this album is streaming on NPR right now and fantastic.

Click here! NPR Music: The Mountain Goats, All Eternals Deck

Tennis: Cape Dory

February 3, 2011

Tennis: Cape Dory

Artist: Tennis
Album: Cape Dory
Label: Fat Possum Records
Release Date: January 18, 2011

Read the rest of this entry »

Building My Hackintosh

January 17, 2011

Not to be confused with last week’s “My Hackintosh Build” post which can be found here. That post details the exact hardware, the cost, and compares it against an iMac with similar hardware. This one is about the actual work of building it and getting it running.

Well, it wasn’t quite as easy as I would have hoped, but I’ve made it. I am typing this post on a brand new Core i5 computer running OS X. Most rewarding of all, I built it myself. Everything major works. Life is good. Some of you may be wondering: How’d you do it? What problems did you encounter? Was it worth it? This post will answer these questions. It will also serve as a bit of a jumping off point if someone is thinking about building one themselves. Hit the break for a detailed description, pictures and more.

Read the rest of this entry »

(adj) having or exerting a malignant influence

January 12, 2011

Specifically, we are supporting the WebM (VP8) and Theora video codecs, and will consider adding support for other high-quality open codecs in the future. Though H.264 plays an important role in video, as our goal is to enable open innovation, support for the codec will be removed and our resources directed towards completely open codec technologies.

– The Chromium Blog

Not Evil

Google believes in the openness of the internet. They idealistically believe in supporting only 100% unambiguously royalty free video codecs. H.264, while close, does not meet these standards. It is controlled by an advisory board that has made a commitment to have no licensing fees ever, but only for non-commercial use. For Google (and Mozilla, which has already taken a stand against H.264) this isn’t good enough.

For these reasons, Google will be phasing out support for H.264 in Chrome. This move will accelerate the implementation of the WebM standard and help ensure the longevity of free codec use on the internet. Google will do their part by converting their YouTube videos all to WebM and for the foreseeable future making them capable of running in Flash, H.264 and WebM until WebM achieved parody with H.264 technology in terms of hardware acceleration, stability on mobile devices and battery life performance. Once that happens, Google and their services will stop supporting H.264. We believe that these standards are achievable and will work our hardest with software and hardware companies alike to make this a reality for all users on all platforms.


Google will do almost anything to handicap iOS at this point. It is already on its way to the lion’s share of the smartphone market and it wants to keep it that way. It wants to do to iOS what Windows did to the Mac OS: sub 10% smartphone market share

What better way to do this than to leverage its three most valuable assets: Chrome, YouTube and Android. They haven’t announced lack of support for H.264 in YouTube or Android yet, but it is only a logical extension to their current rationale for dropping support for the codec on Chrome. Once this happens, browser makers far and wide will start suporting WebM videos. Content producers will do the same. Knowing that older browsers don’t support that format though, Google hopes that they will turn to Flash as their backup. This covers pretty much everyone on the desktop, but who does it leave out on the YouTube fun? iOS users.

In an effort to marginalize iOS’s market share, Google is willing to announce the removal of support for the most popular video codec in use today. Let’s make this clear. Google is not omitting a popular feature from a future product, as Apple did with Flash. They are removing support of a feature from an existing product. People who use Chrome today have support for H.264. People who use Chrome a year or two from now won’t.

By the time that Chrome no longer supports H.264, Google hopes (fingers crossed!) that the WebM standard will have gained hardware acceleration support, stability on mobile devices and have a minimal effect on battery life. Then, they can put it on Android phones which will likely have a significantly larger market share than iOS devices by this time. Steve Jobs expressed disdain for WebM in the past and Google hopes that he will be too stubborn to go back on them when (if?) WebM achieves parody with H.264.

While all of this is happening, Google hopes more developers will go back to Flash. That’s something that everyone who is afraid of Apple can support, right?

Like all polarizing arguments, the truth probably lies somewhere in the middle.