“The Microsoft license specifically excludes software under the General Public License, commonly known as the GPL. The GPL is the software license used by Linux and by SAMBA, a popular open-source program that allows non-Microsoft systems to share files and printers with Windows.” Read the rest of the editorial at ZDNews. Our Take: Funny. Everyone is getting worked up with that CIFS license, and it seems that no one has actually read the new Visual Studio.NET license. We did so with my husband 1-2 weeks ago. We are not lawyers, but what we pretty much understood from it, was that you can’t develop and/or distribute GPL or LGPL (or compatible licensed) applications created with Visual Studio.NET. I personally believe that this is more important of the CIFS license issue, because it pretty much takes out any possibility of creating Free software for the Windows platforms, when using either the classic Win32/MFCs or .NET APIs. And if you are thinking about using Gcc, bad luck. The license prohibits using a GPL-compatible license for your apps that link against Microsoft’s libraries. Quite possibly Microsoft used such restrictions in order to protect themselves from the possibility that someone may ask them to open source their technologies if third party developers link their GPL apps with Microsoft’s libs, but on the other hand, it is restrictive to not be able to use a $1000 developer’s tool to create applications the way you wish.