The experiment did not go as well as I might have hoped, and despite my efforts to stick with it for some time, I eventually had to cut the experiment short. As I was preparing to re-image my system I started a blog post which I decided not to post at the time. I’ve included a short excerpt which shows my state of mind back in May, just after the experiment concluded.

I told myself I was going to stick it out for at least 3 months. But here I sit, not 3 weeks after making the decision to migrate my primary machine to Ubuntu, with the Windows 7 installation disk in hand. What could possibly have brought me to this point? Primarily, time.

It’s going to take me about 8 hours of work to prep all the data on my system for the transition, wipe the linux partition, re-install windows, re-install the applications, re-install VMWare, re-install my Linux VMs (I do still have a use for them!). The problem is, things on linux generally have taken longer than they should. Some of this is due to the fact that I’m learning, and I’ve tried to ignore those. Others are generally due to the fit and finish of Ubuntu.

So what went wrong?

Problem #1 – 10.10 or 11.04?

I generally resist the temptation to move to the latest OS release, but when I tried setting up a Windows VM under VirtualBox in Ubuntu 10.10 the audio was mucked up. It seemed a bit slow too, but that may have been my imagination. So I tried installing the newly minted 11.04. The VM now worked like a charm, but that was a long multi-step process.

Problem #2 – Virtualization

Trying to set up a virtual machine that would start up at boot time (like a Windows service or any number of linux daemons) proved a nearly impossible task. After several hours of searching, tweaking, testing, and ultimately failing, I decided to abandon the effort and live with manually starting my VMs.

Problem #3 – File Sharing

Setting up network shares was probably one of the better experiences I had. I was able to set up a “public” share on the linux machine and access it from anywhere on the network… as long as I didn’t want to protect it with a username and password. That was going to require more voodoo and black magic than I was prepared to endure for such a simple task. Overall, not a bad experience.

Problem #4 – Flash in Browsers

Like it or not Flash is still an integral part of the web, and Flash in the browser was just one of those things that never quite worked right. When I talk about fit and finish of a product, this is what I mean. Blocky artifacts showing up on video players was the most common issue, though there were other things like playback and audio problems as well.

Problem #5 – Lack of Air Support

The fact that I felt compelled to write a blog post calling attention to a tutorial for getting Adobe Air installed under Ubuntu 11.04 speaks to just how difficult this didn’t need to be. On any other major platform, you can go to a website and simply click the install button. The rest is automatic. Not here though.

Problem #6 – Button Clicks

I constantly had problems just clicking on buttons. Sometimes in an application (Chromium comes to mind) but sometimes just within the Ubuntu environment itself. This kind of thing makes you start to question the faith you have in your OS.

Problem #7 – Learning Curve

I suppose it’s a bit unfair to put this here as it’s undoubtedly the same issue that would come up moving between any two major operating systems. The bottom line is that I have a young family with whom I like to spend the majority of my day. That means that when I decide to sit down at the computer to do something, I don’t really have the time to spend learning how to do things all over again.

There were a few things that were also pleasant surprises during this whole thing. Mostly to do with 3rd party applications.

CrashPlan support

CrashPlan was able to seamlessly match up my Windows backup to the Linux file system. This made it very easy to move everything over. I just hope it works as well in reverse.

AcidRip

Digitizing DVDs has never been easier. It took a couple of tries to get the quality settings just where I wanted them, but the process worked out really well.

Shell

I love the *nix shell, Bash in particular. This is the one thing I will truly miss when I move back to Windows. Having commands like rsync at my disposal, and built in SSH support are also fantastic. While this is something that has to be hacked into a Windows installation, it is available by default on OS X.

In summary…

The availability of good software to do most tasks is one of the key benefits of moving to an open source experience, but the truth is that the experience really didn’t live up to my hopes or my expectations. I’m getting to the point where I want my computing time to be spent creating, not just experimenting with different ways that I could set up my tool sets. And as time moves on, the number of free or open-source applications available on the major commercial platforms like Windows and OS X is growing. Once either of those operating systems is installed I can do everything I want to do without having to pay a license for another piece of software — and in many cases the applications are as good or better than the open-source tools available for the Linux platforms. Add to that the growing number of applications which reside in the cloud and are completely browser and platform agnostic and it starts to become a simple equation for me.

Is it worth the $150 or so that it costs to get my new computer preloaded with a commercial OS? Yes.

I’ve been looking for a better way to do my Windows dev work at home for a while now.  I’ve explored a few different options including VMs and Mono, none of which suited the needs that I have.

I’m not someone who has to have the latest & greatest computers to get my stuff done. The things I use my computer for don’t require a whole lot of horsepower. Truth be told, the newest computer in the whole house is my three-year-old Macbook. So when it came to deciding which of the three machines in my house were going to get the Windows 7 treatment it wasn’t hard to decide.

Apple has said that they won’t be providing official support for Windows 7 on any of their machines for another few weeks, and when they do it’ll be on a limited subset of their Intel-based machines, and only for customers who’ve shelled out the extra $30 for Snow Leopard. Admittedly I’m not an expert in computer hardware, but I’ve been around the block enough times to know that “not officially supported” doesn’t mean “it won’t work”.

The first thing I tried to do was just clear some disk space and run the boot-camp wizard to set up a partition for Windows. Once again I ran into the problem of OS X not being able to reorganize the files on disk to create a contiguous partition. This doesn’t usually pose a problem with computers that have a disk defragmenting tool but of course OS X has some redimentary defrag technology built-in and thus the notion that “Mac’s don’t need to be defragged”. I call shenanigans.

Once I resigned myself to the fact that the only way I was getting back to the nirvana of dual booting was going to be to re-image the Macbook again, I backed up the system, procured a copy of Snow Leopard and got started with the process. Reinstalling OS X was about the same as with Leopard. A couple of new options but nothing earth shattering. The Windows 7 installation on the was also nothing special. Smooth and straightforward as we’d expect out of any modern OS, but it did move fairly quickly.

If you happen to be reading this before you do your installs there’s one useful piece of information in the 14 page document that Apple says you need to read before trying the scary installation of Windows on your Mac. That would be that the drivers for Windows are located on your Snow Leopard install disk. I spent about 3 hours trying to find drivers.

Even though Apple says Windows 7 isn’t supported, the included drivers on the Snow Leopard disk (intended for use with Vista) work just fine.  Windows also reports that some drivers fail to install properly, but in my case there’s nothing overtly wrong. Network, audio, video keyboards & mice are all working as expected with the exception of multitouch functionality on the trackpad. Since I’ll be using the Windows side of the machine most often when connected to a full desk setup (KVM) I’m not too worried about it.

If you’re interested in some background you can check out the original post I wrote explaining the experiment.  The key lesson with all of this however is that Content is King (or at very least a Duke) and you need to respect that above pretty much all else if you ever expect to get ranked.

It’s a pretty simple proposition really, I’ll put together what I know about SEO with regular posts to the site.  Hopefully between now and next Friday night I’ll be able to get the site on Google‘s radar.

What are my chances?  No idea, but you can check out the post explaining the Google – WordPress experiment on the new site at kickjoey.com.

I’m relaunching with a bit of a project in mind: get this site from a PageRank 0 to a PageRank 1 in 7 days.  Impossible? Probably, but I’ll try it anyway.

Why PageRank? Because I’d like to start doing reviews here that I can collect on. Yes, paid blogging. I didn’t really want to to advertorial posts on kdmurray.net, but it’s something I’ve wanted to try out.

What next? Well, time to find some content to do reviews on over the next 7 days, and try to get some links pointed here from some other websites.

Let’s see if we can get this site on Google’s radar in only 7 days.