Skip to main content

The difference between Vista, XP, Linux and MacOS explained!

I was looking around for some nice articles to read till I reached this funny yet real blog post from Phil Shapiro on

The Difference Between Vista, XP, Linux and Mac OS Explained
Wherein a middle school student asks me to explain the difference in simple terms. I do just that.

A middle school student I know asked me to explain the difference between Vista, XP, Linux and Mac OS. Here's the gist of our conversation:

Me: "You want to know the difference in real simple terms? Okay. Vista is bad gnews and GNU is good gnews. XP ain't such bad gnews, until you reach the blue screen of death, which ain't good gnews at all."

Middle schooler: "Okay, I think I understand. How about Mac OS?"

Me: "Mac OS is like a beautiful Bermuda island with a prison wall built all around it."

Middle schooler: "Really? How so?"

Me: "Well, Mac OS uses Digital Recreation Management (DRM), so if you want to build a sandcastle, you are forced to use an approved pail."

Middle schooler: "An approved pail? I want to use my own pail. That sounds to me like it's beyond the pale."

Me: "That indeed it is. It's beyond the pale. To use an approved pail is going to cost you $40 up front. Would you like to use Mastercard or VISA?"

Middle schooler: "I don't want to use Mastercard or VISA. I just want to use my own pail."

Me: "It sounds to me like you're ready to break out of prison and live a life with no bad gnews."

Middle schooler: "Yes, I'm ready now. I'm ready for that. Will you show me how?"

Me: "Well, sure, I can show you how."

I just love how he spelled GNEWS (news) , so GNUish.


frex said…
it is still not clear for me.
Marvin said…
hi frex, obviously the guy is a linux guy with all the GNU'sh term he is using. the story was more focused on how open the systems are in terms of the source code and the opportunity for integration.. apple being the "most closed" system , windows being next and linux as the "most open" system :)

Popular posts from this blog

Hiding Unwanted Python Folders and Files in Visual Studio Code

Visual Studio Code is a universal editor and pretty good at it. However, the explorer view maybe cluttered with the automatically generated folders and files confusing developers. Python is no different. Below are example files and folders generated by Python.

The __pycache__ folder and *.pyc files  are totally unnecessary to the developer. To hide these files from the explorer view, we need to edit the settings.json for VSCode. Add the folder and the files as shown below:
Copy and paste the lines below :


renaming default namespaces for VSTO projects in VS2008

So here is the scenario , you are starting a VSTO project and decided that your default namespace is ExcelAddInTesterApp . You created the project and started coding the project. After several days , your boss called and said "hey marvin , make use of this namespace OurCompany.ExcelAddInTesterApp , we have to add our company name to it got it?" . You get back to your machine thinking its just a simple property just like any project you've been working on. So you right clicked the VSTO project and hit properties . Boom! What the F@#$? The default namespace textbox is disabled!!!!

I've been through this and I googled for ways to do it and ended up with a blog from a Microsoft MVP telling me it can't be done because it is disabled. Then I thought of Refactoring, the beauty and grandeur of the renaming process. I selected the namespace and hit the refactor menu hoping that this would solve the problem . Unfortunately , it did not rather it displayed the message box …

Getting Started with Stateless : A Lightweight Workflow Library Alternative for .NET

A year ago, I was looking for a simple workflow manager for a project I was working. Its a medium sized application that involves tracking the state of assets in the system. Back in 2008, Microsoft (MS) introduced new technologies along with the release of Visual Studio 2008: Windows Presentation Foundation (WPF), Windows Communication Foundation (WCF), and Windows Workflow Foundation(WF). Having worked in a company utilizing mostly MS products for development, my first option was to go with WF. After doing some time reading and studying the library, I paused and decided it was too complex for my requirement. Using WF would be an overkill and the fact that it has, a rather, steep learning curve, there has to be another option. My mind toyed with the idea of developing a simple workflow library myself. It would be a learning experience but it might end up consuming a lot of time.

Why reinvent the wheel? So I started querying the internet for a better solution. I stumbled upon Stateless