This driver, if I understood it correctly, has no other purpose but to enable a proprietary VM to work with the kernel (correct me if I'm wrong). If I'm right, I see no reason why it should ever be included in it.

This seems like very odd logic as if followed through, we shouldn't allow any drivers into the kernel. Every driver in the kernel has the express purpose of making a proprietary piece of hardware work in Linux, whether coded by the manufacturer or not. The truth behind your statement is exactly what Linus was referring to, the "M$ Disease." Simply because it is Microsoft you feel the complete and utter need to bash it. No rhyme or reason. Defies all logic. It just must be done.

This is a great step for the Linux community. I doubt very few people would believe that Microsoft would ever become a contributor to the Linux kernel. They have made an investment now in Linux. That is quite monumental. Those 20,000 lines of code weren't free and they will likely be continued to be maintained. This is an exciting time!

Honestly, I'm not sure why this even matters.

Restarting the GUI in Linux is common because of (at least in my experience) how unstable, relative to the Windows GUI, X and the windows managers are.

The real thing I love is how Windows XP can have its GUI running and all supporting processes and only take up between 85-90MB of memory. To get a similar GUI in Linux requires 2-3 times that much memory.

Ah, I remember Executive Decision. As I recall it was the first Steven Seagal movie that was any good!

It could have been better. Ten minutes with him in the movie was a little long.