Hi,

I work for a webhosting company and we install dotnetnuke for our clients. I absolutely despise the thing and decided to do a google search for “dotnetnuke sucks”. I came across the entry. But yeah, dotnetnuke totally blows. rock on.

-Matt

I landed here by googling “DotNetNuke Painfully Slow”. I agree it’s painfully slow and has many sucky aspects. But at the same time, I can’t dismiss it, although I’d love to find something better.

For professional projects DNN has other open-source projects beat hands down. I have tried several other platforms including few of the PHPNuke forks. So many of the OS projects just are too inconsistent, incomplete, confusing, and generally unprofessional to deliver to my clients.

As far as development environments, I’ve developed in JSP using opensource IDEs, hand-coded PHP, and created DNN modules in VS2003/2005. I’ve got to say that the M$ dev environment is much quicker, more productive, and more thought out.

So my conclusion is that DNN ain’t perfect, but it’s the best thing I’ve found so far. If there’s a better open-source (or low cost) portal system, I’d like to hear about it! But remember, the dev environment counts too!

-Robert

Robert one word JOOMLA!

Technology often appears to suck to people that don’t understand it. As for the speed of DNN, I suggest you look into a concept called “precompiling”. Programs often run better when they are compiled. You see, humans code in languages and those languages can often be interpretted on the fly. That is OK for newbies but when newbies start compairing oranges to apples, they may being to think an interpretted system sucks when, in fact, it should be compiled for the platform. Poor newbies, they just don’t know any better.

DDN isn’t for morons. Moron’s don’t know how to deploy systems. DNN also isn’t for hacks that don’t understand fundamentals.

I am working with DNN from its 3.x version. It is amazing the amount of errors I have encountered developing apps to DNN. I built a middle.sized project on top the DNN framework, and I painfully maintained along the time. In the meantime, I had to upgrade DNN, I think a dozen of times, changing from version to version, changing from Visual Studio 2003 , to 2005 now 2008, Changing from .Net 1.1 to 2.0, and every time, EVERY TIME new errors were emerging from DNN framework. I ending dealing how to solve the DNN errors instead how to build my app.

I think that DNN SUPER sucks. My biggest surprise was when I begun to program to Linux/Mono/PHP/MySql, etc. I tried a few programs… I just couldn’t believe that I installed those software and I had NO errors (every DNN installation is a pain in the ass).

Last thought: I think that DNN is a very over-sized architecture, too much variables to consider when you install, and a pain in the ass to extend and mantain.

And yeah if somebody needs some documentation about trouble, I have plenty of them and many ‘workarounds’.
This post is the result of the problem i had installing DNN 4.8.4 who has a nice bug. We’re talking August 2008 . How many version of DNN do you need to do the things right?