The way I see it is that the main difference between Oxite and DotNetNuke is that Oxite is aimed more at the developer (http://www.codeplex.com/oxite/Thread/View.aspx?ThreadId=41785) . DotNetNuke can be used by non developers right out of the box and then extended by developers.

However, one weakness is the level of visability of DotnetNuke to the general public.  Do a news search on Google for say DotNetNuke (42 items in the past month), Drupal (528 items in the past month), Joomla (585 items in the past month) and Oxite (78 items in the past month) to see what I mean.  I don't think the release of Oxite will increase the exposure for DotnetNuke. Though it does provide the opportunity for more comparisons which hopefully will include DotnetNuke.

With the recent funding and ramping up of the Corp and DotNetNukePro this should also increase the exposure.

Increased Competition is a 2 edged sword especially when the new kid on the block is backed by or percieved to be by one of the largest corporations.

my 2 cents

Antony

DotNetNuke has always been a showcase for making practical use of new Microsoft Technoloogy and/or design patterns.  Since MVC does not fit well in with current DNN architecture (you can read Charles blog on MVC), it needed a showcase and Oxite is it.  There are many platforms for us to keep an eye on and Oxite will be added to the list.  But until it has significant adoption, professional support, installed and active user base, 3rd party aftermarket, commercial extensions opportunties, etc... I would not get too excited about it ;)

Cheers,
Scott

Scott Willhite, Co-Founder DNN

I have played around with Oxity and other MVC sceleton and for the moment they are just showcases, Oxity a rather good Blog machine. I have not yet get any speed to do nice programming in MVC but there are things I like in the new dev. platform.

True or not I think today DNN looks old and not in phase with new technologys if you look at it from the outside. Personaly I had tryed to implement some new features in DNN to faster adopt what is happening out there. First of all I had done the following.

Implemented a webservice who module developer could adapt(webserver extention) for ther modules. This first for Silverlight. (Amazing product by the way).

Adapted Linq to SQL (time to get rid of object q ?)

I could add a few other things but those two I had started with.

Its rather easy to do this in a single project but if not DotNetNuke have this as a "standard" people will look at DNN as old , wrong in my opinion but thats life.

Jan