In my ever ongoing efforts to completely shed all connections to Microsoft Windows and all Windows applications, including 3rd party ones, I've been doing a lot of research over time into various methods by which I could make that one final push to completely shed all of those lingering connections. But alas, it's been much harder than I could have expected. That's not to say it's impossible, but there certainly seems to be a lot of things out there bent on NOT letting me make that last step. So it's less an issue with what I'm doing or not doing, and more a case of forced adherence to a system I'd like to separate myself from.

There's many reasons why I want to rid myself of this connection. Here are the three biggest that I believe drive this interest.

1. Viruses - I may not see many viruses on my system, but then again I'm also very alert to what's happening and I'm constantly keeping all my defenses and protections up to date and running well in order to fend this off.
   
2. Spyware - I can't even begin to tell you how much I abhor spyware. Be it intrusive web ads, spyware apps, malware, or any of a variety of other things.
   
3. Proprietary Software - Now not all proprietary software is bad. However, the main platform it runs on and the vast majority of applications written to run on it are. There's little to no accountability from the OEM (unless it's forced by the end users, and even then that accountability is weak), and issues are handled on a "money" focused, rather than "end user" focused priority.

That's why I'm so interested in Open Source software systems, including operating systems (Linux, BSD, etc), end user software (Firefox, Open Office, etc), user interfaces (KDE, Gnome, XFCE, etc) and so much more. The software is open, the developers are accountable to the end users, and the software tends to be more secure and reliable. Those developers who choose not to do the will of the community, unless it's for the better of the community, tend to be abandoned and left to atrophy while good projects that do keep themselves accountable to the user base succeed.

But enough with this little sermon. If you're reading this, you likely either already know about this, or have heard enough to know the facts. So I'll move on to the main focus of this article. Comparing the two major forms of in-system emulation of Windows applications. No matter how hard you try, unless you've committed yourself to giving up any and all Windows based applications, you tend to find yourself stuck in a situation where you must emulate at least one of these applications inside of Linux. This is where emulators such as Virtual Box and Wine come in handy to help you bridge that divide.

The best way to understand the pros and cons of doing something like this vs going "cold turkey" on all windows applications is to look at the pros and cons of each of the emulation systems and see if they meet your needs, or if you may have to take more drastic steps such as dual booting or other such measures. Below I've created a list of all the pros and cons I've come up with for Virtual Box and Wine, the two main emulators out there. I've also included a third line for "dual booting" for comparison.

Pros:

Cons:

This list is just a summary of some of the pros and cons of using these two different methods for running Windows applications in Linux. Now again, dual booting is not an emulation method to allow Windows applications in Linux, but it does provide a comparison between the two emulation methods, and a natively installed system, even if it is technically dual booting. Now if you're wanting to run games in Linux, some of what you run into is hit and miss success. Here's some examples of some common newer games vs older games and how they run in the two emulation systems. This isn't a complete list by far, but it does provide some comparisons.

Again, this list is just a sampling based on some stuff I had on hand and doesn't cover all the games I tested, but does provide a sampling that best represents the general experience overall. So it hopefully it gives you an idea of what you're up against. Overall, I'd say that the games I had the biggest issues with were the Microsoft games. Not surprising really, but disappointing none the less. The ones I had the best luck with were the Blizzard games.

Now on the question of applications, that varied quite a bit, and while some ran well, others were an utter joke. Here's a sampling of the programs I tested and generally how they came out.

Again, this is just a sampling of what I tested and they are listed in the most representative manor to relay what I ran into during testing in the best way possible. The "good", "great", "poor", etc ratings count both performance and stability into one rating since stability without performance or vice versa really doesn't make for a good experience. Both have to be good to get a good rating. Overall though, depending on what you need to do, I feel that from my testing the better choice overall is to use Wine for all your emulation over Virtual Box. Sure, Virtual Box with an emulated copy of Windows XP can give you some flexibility that Wine doesn't have.

However, given the legal and licensing entanglements, it may be better to use Wine for everything you can, and then just run the rest via a dual boot setup in a native Windows environment until either Wine does everything for you, or you no longer need that application or game anymore. Now I did like Virtual Box and all it offered, but given all the potential licensing entanglements, plus the fact that you're running a restrictive proprietary OS inside a free and open source operating system, even if it is emulated, it's still a rather questionable ethical and legal choice.

I hope this has been a helpful overview and if you have any questions, please feel free to ask in the forums. Thanks!