This issue has been coming up for a while now, and there are still people asking “why would Microsoft lock up the Zune? Wouldn’t custom firmware, HD access, and the like be a tempting feature set to garner sales?” It’s an interesting point, but before we can delve into this, we have to understand the difference between open source and closed source development. Both have different purposes, goals, and ultimately, executions.
Open source is built around the spirit of community. It is when developers open their code to a wide base of both users and other developers. More often than not, these open source projects have been released free of charge. The purpose of open source development is to draw together community development and growth. The ultimate goal of any open source project can vary, but it is most likely some variant of the “let’s see what we can make together” philosophy. No open source project ever has to die, so long as there is a community of coders who spend their time in keeping it updated and in development. Many open source projects are collaborative, with users contributing individual pieces of code to a larger project. There’s a place for everyone in an open source project, since any and all contributions to the knowledge and code base of that community can be helpful. Community and the ever-present pursuit of knowledge are what drives the open source movement.
Closed source development takes a sharply different angle on the issue. Closed source development isn’t made with any community in mind, but rather, the customers. Closed source development is a business, where a final product must be released, like any other product on any other market, and those who purchase such software have certain expectations of the product in question. They pay money for a certain standard of quality. The idea is to create a single product that will satisfy most of the intended audience most of the time. Ultimately, the goal is to make profit, just like any other business; to do less would be folly. Simple business and economic sense would dictate that in order to have a successful business, you must make a product that can appeal to a wide market and have a return high enough to garner an economic profit. If you come out in the red, well, you’ve just wasted perfectly time and money on a fruitless pursuit and come out with less than you went in. No sane business wants that to happen. As a result, any software made for profit will be under the control of the business responsible for it, and is almost by default closed source. The only freedom you have with that software is within the intended boundaries set by the business marketing that good, or if you can get lucky, you can break their limitations through “hacking” and do more. No closed source developer likes to lose control of their products, their work, their code. Once the project becomes “open,” it’s hard to go back. It is quite likely that the developer will actively work to thwart the attempts of these hackers, as has been shown with the battle over the PSP: with each new firmware released getting hacked, then a new one is released to combat that hack in a never ending cycle reminiscent of that between armor makers and weapon makers.
So, quick recap: open source projects are centered on the idea of a community, and closed source projects are often centered on the idea of a business. Now that we have that settled, let’s move on to the Zune itself.
The Zune is a closed source development, no if’s, and’s, or but’s about it. Microsoft is a closed source developer and a business, which is equally apparent. They have a vested interest in guarding their products from being used in any way they don’t approve: it’s how they make money, and thusly how they “succeed,” how they accomplish their goals. They created the Zune in order to gain profit. They are looking to satisfy customers, but only enough customers. Yes, it would be nice to have features like hard drive access to the Zune. It’d be nice to sync the Zune with any WPD compliant music software. It’d be nice to run RockBox on it. It’d be nice to add support for missing codecs and character sets. It’d be nice to add all sorts of functionality to it. But the Zune is not our product, not a part of any community. It is Microsoft’s product, which they developed as a tool to meet their end goal, the goal of all sane and successful businesses. Microsoft is building a product in an attempt to satisfy the average customer who is out looking for a quality PMP. Yes, these enumerated features and so many more have all been asked for by consumers at one time or another, but money doesn’t lie. People are willing to pay $250 for that shiny, brand-new Zune 120. People pay that price hopefully with the full knowledge of what the product they’re buying actually is. If Microsoft is making a profit off their product, well, that’s all they ever set out to do. And the Zune, even though it is still struggling against the dominant iPod, is finally making a name for itself. More than two years after its release, it’s ceased to be the laughingstock it was once known as-let us rest the analogy “squirting” tunes to each other right here and right now-and is now gaining some real mainstream acceptance. In fact, a member of the Cnet crew, a widely known tech news, review, and download site, has completely switched over to the Zune, and multiple tech sites now sing its praises left and right, despite shortcomings such as battery life or Z2K9. It’s doing what Microsoft wants it to, and ultimately, that’s all that matters to them, and that’s just fine. We can moan and complain about how they are somehow “cheating us” of features that for some reason need to be on Zune, but that changes nothing. The only reason to get upset at Microsoft is if the device you received does not do what it is supposed to do. If that’s the case, there’s always the 1-year warranty, which is there for exactly that purpose. They cover any issue that is not directly caused by the end user, when it is their fault for the error. If your Zune up and gets an error code 5, it’s probably their fault, and they’ll fix it.
Now, after talking about the Zune itself, let’s touch on Zune games. If the games are open source, should the closed source restrictions be allowed to affect them? The answer is a definitive yes. It’s true that there are many open source games available for the Zune, and free of charge at that, but they are being developed for a closed source system, and thus must fall within the restrictions placed by the closed source developer. Microsoft is clearly afraid of games being used to hijack their platform, be it through some direct attack, or perhaps to simply commandeer Zune Pass and other copyrighted content freely. They not only want control over their platform, but they also strongly want it to be considered a reliable platform to record companies when bargaining for contracts to fill the Zune Marketplace. So yeah, it does kinda suck that our games have to restart and can’t access DRM’ed content. But we can’t blame Microsoft for that, it is both expected and necessary. Better to have restricted access than no access at all.
In closing, remember the quote the started all of this: “Why would Microsoft lock up the Zune? Wouldn’t custom firmware, HD access, and the like be a tempting feature set to garner sales?” The answer to this is simply, yes, they are tempting features, but until Microsoft comes up with a way to foolproof them, it’s not likely we’ll see them on the Zune again, if they can help it. Again, the Zune is being designed for the average consumer with enough compelling features to appeal to a wide audience. Microsoft will naturally aim to include as many features as they can on the Zune, but there are just some places they don’t want to go because of the closed source philosophy and business model. Perhaps it’s flawed, perhaps it isn’t, but in the end that will be determined by where we, the consumers and Zune owners, choose to put our money. If the Zune becomes a success, as it is on the road to doing, then Microsoft did a good job, even if we didn’t get quite everything we wanted. Making any product to be sold on the market is a daunting task and a daring risk. Microsoft took that risk, at the added hazard of releasing hardware, despite their focus as a software company. It’s not a perfect product, and it’s not for everyone, but it’s a product that’s doing well, especially in the iPod-dominated market of PMP’s. So for now, let’s just sit back, wait, and see what happens, and maybe, just maybe, we’ll get those fancy features we’ve been begging for all along, when the time is right.