Apple, Video Games, and Disruptive Markets

Posted by: TomS on January 28, 2011 @ 7:36 am

AppleAt lunch the other day, the conversation turned to Apple, and one of my co-workers posed the question, “Why hasn’t Apple released a video game system yet?” At the time, I was playing Angry Birds on another co-workers iPhone, and I waved the iPhone at him and responded “They have.”  He of course responded that it isn’t really what he meant, but I thought a bit more about what Apple has done with its gaming strategy up till now, and they are actually positioned surprisingly well to pull in a huge chunk of the video game market over the next few years.Angry Birds

Before I dive into the details, most of my argument is based on Clayton Christensen’s ideas around disruptive innovation and low-end disruption. In a nutshell, Christensen theorizes that most disruptive innovation occurs when established firms neglect certain market segments because they offer too low of a margin to entice the incumbents.  Innovators enter the low-end segments and the incumbents do not react, but overtime, the entrants overshoot the needs of the low-end markets and begin to pick up additional market segments.  Left unchecked, the entrants eventually overtake the market, driving the incumbents out completely.  Its a pattern that has repeated itself throughout history, and Apple may be repeating it again with the growing library of games it distributes on the App Store. (more…)

Setting up a New SVN Repository

Posted by: TomS on January 9, 2011 @ 12:44 pm

It’s been a while since I’ve had to set up a new SVN repository on my home network, so now that its time, I figured I write a quick post documenting the steps along the way.

For those that may be unfamiliar with it, SVN is a commonly used version control system.  It allows users to manage the changes to source code over time so that a user can quickly restore old versions, analyze change sets, and control how change sets are applied to a set of source code.  SVN is likely the de facto open source centralized version control system.  It grew up from the older CVS project, but it should be noted that it is a centralized version control system.  There a number of distributed version control systems out there such as git, Mercurial, and Bazaar, which are gaining adoption very quickly and provide a number of benefits for projects with many users.  For my home use, I’m the only user, and I’m familiar with the ins an outs of SVN, so I’ve stuck with it.

SVN is also one of the most well documented open source projects out there, primarily because of the excellent work that goes into the SVN Book.  The online content is freely available, and its essentially the same content that is published in the O’Reilly reference.  It is update often and is very comprehensive.  If you have any questions about SVN, I’d start there.

Now that I’ve gotten that out of the way, on to the content.  I want to set up an SVN Repository for a new project I’m working on.  There are a number of ways in which you can choose to organize SVN, but I generally follow the 1 project per repo model.  I use Apache and WebDav to connect to my SVN repos so that I can access them directly over http.  Assuming you already have SVN and Apache installed, there are really three quick parts to the setup.  Create the SVN Repo, Configure the WebDav connection, and Setup the SVN Repo.

Create the SVN Repo

To create the svn repo, you’ll make use of the svnadmin command line tool.  It provides a number of SVN mainteance functions including the create repository functionality.  I usually create the repository as root, and then after it is created update the permissions so that the web user is the owner and the group is the SVN group.  This allows both Apache and SVN processes access to the files.  The commands needed to set this up are below.

#create the new SVN repo
sudo svnadmin create /storage/svn/myNewRepo/

#change permissions on the new repo so that Apache and SVN can access it
sudo chown -R www-data.svn /storage/svn/myNewRepo/

Configure the WebDav Connection

Creating the WebDav interface is also just as easy.  You’ll create a simple Location entry in your Apache configuration which defines the parameters needed for users and the SVN connection.  For me, I put the configuration in the default website on my SVN server (on Ubuntu its /etc/apache2/sites-available/default), and I use the Apache AuthUserFile to control users of the repo.  I have set up user accounts for other repos, so I’m just going to hook into the existing file.

The location information in my Apache file is shown below.  I add it directly the default VirtualHost listing for the server.

<Location /svn/myNewRepo>
   DAV svn
   SVNPath /storage/svn/myNewRepo
   AuthType Basic
   AuthName "Subversion Repository"
   AuthUserFile /etc/apache2/passwords
   Require valid-user

From there, its just a quick Apache restart with sudo /etc/init.d/apache2 restart and then you should be able to access the repository over HTTP in your browser by going /svn/myNewRepo on your server (i.e.  You should see a simple page listing the repository information, version 0 as the version number, and an empty directory since we haven’t added any content yet.

Setup the SVN Repo

Your svn repository is now ready to use.  Most repositories follow the general pattern of a trunk/branches/tags structure, so to make sure things are working, I’m going to create those directories using the svn command line client.  Thereare a number of ways to do this, but I’m just going to create one directory at a time directly on the server.  The commands look like this.

svn mkdir --message "Creating the basic SVN structure for the project"
svn mkdir --message "Creating the basic SVN structure for the project"
svn mkdir --message "Creating the basic SVN structure for the project"

And that is all that’s needed.  You can verify that it worked by going to the svn repo’s web address again and verifying that the list of folders has updated.  Typically you would then check out the SVN trunk and then start checking in your code.