That's what I'm saying though. Nobody has a Xerox PC, and very few people have a Mac. It's great that they did what they did, but their own implementation never became mainstream. If Microsoft knows anything, they know business. They know how to be profitable which helps developers along the way. My two biggest problems with DotNetNuke, is that I was learning a tool set that would not be very valuable to me when, I could have been concentrating on other areas. The other issue is that it seemed to reverse the headache points in building applications. It made everything that was difficult very easy, but it made the simple things very difficult.

Live free or die.

I meant what I said, when there is a major revision of .NET you will have to wait until DotNetNuke updates it's core. Try running DotNetNuke written in version 1.1 of the Framework in a 2.0 site...doesn't work. Also it's impossible to include C# code files in a C# module. You have to create a separate project/dll for your module if you want a C# code file that's not a code-behind file. That's ton's of fun. Just because skins came before MasterPages doesn't make them better. It reminds me of Apple user's gripes that Apple had a GUI before Microsoft. Who cares!? I means seriously, how relevant has Apple's PC market been just because it did something first?

Live free or die.

You're going to be behind and sacrifice a lot of new technologies like Linq and new versions of the .NET Framework until they decide to port the core. You sacrifice a more standard set of technologies like MasterPages for the DotNetNuke implementation of skins. I recommend you listen this MS podcast by DotNetNuke founder Shaun Walker himself for more info. http://download.microsoft.com/download/4/E/F/4EFC8904-82E7-4BA2-A7BC-F6759FAFF9FE/1032359088.mp3[^]