Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Website Critique condemns the use of ASPWebsite Critique condemns the use of ASP
Previous
 
Next
New Post
3/27/2008 10:23 PM
 

I just finished migrating a customer of mine into a Dotnetnuke site.  Because they are a high-profile dealer for SeaRay Boats it is important that their website reflect this high profile.  There is still a bit of work to do, but the website was recently subjected to a Critique by a consulting company hired by SeaRay.  They really could not find any major shortcomings, but they recommend that PHP be used instead of ASP.  Here is what they said:

"The ASP language that the site is coded in can be sluggish and ASP limits the type of webserver your site can be hosted on if you ever need to switch hosts.  If you are considering a rebuild for your site down the road I would recommend having it coded in PHP which is much more universal and flexible for hosting options."

A statement like this does not seem to me to be something a hired consultant should bring up.  The end result is much more important than language it is written on.  I don't see ASP dying off any time soon, but he is right about the sluggish performance.  I turned on the Whitespace filter and it is more perky now.  Is this sluggish feeling inherent in ASP or is it a Dotnetnuke phenomenum?  Do other CMS platforms/frameworks suffer the same way? 

I do everything in DNN now no matter the size, I am just so comfortable with it.  Does anybody have any thoughts or comments?

 
New Post
3/28/2008 12:30 AM
 

Seems obvious: The consultant is fishing for future business with your client and PHP is what they know.

Tell them to f*** off

Rob

 
New Post
3/28/2008 3:35 AM
 

+1 rob

As an ASP.NET programmer I know next to nothing about PHP.  I wouldn't slag if off though, because I don't know if it's fast, scalable or able to lay golden eggs.  I would expect the average PHP programmer to be the same in reverse, *only* with a good chance of a 'i hate microsoft' attitude imprinted somewhere.  The way the discussion is about asp and not asp.net means that possibly he isn't aware that there has been a completely different version of ASP out for 6 years now.

If the question comes up again treat it with the contempt it deserves and brush it off, don't try and answer to the point raised.  

 
New Post
3/28/2008 10:03 AM
 

Mike,

Just for the sake of discussion, who is the consulting group?  As mentioned earlier, the fact that they are talking about asp rather asp.net says a lot about what level of expertise they have.  If your client wants your take on it, ask the consultant to give you the data on which they base their findings.  You can say a lot of things, but the truth is - if the site is doing what the client needs and is flexible to expand to areas they envision, then that's what matters most.  Yes, it's true that finding hosts for asp.net may be more of an issue than finding php host, but that doesn't translate into to a 'better host' or more capable host, or even a more secure host.

I've worked with both types of sites, and each has their own set of positives and negative, but in the end, it comes down to return on investment (ROI).  Just having a site up doesn't mean a thing until you start analyzing what impact (positive hopefully) it has on your business.  The DNN framework alone doesn't give a site ROI, it's how it is used, its' flexibility, and administraion costs that proves the long term value. DNN is built to leverage the very capable server and .Net infrastructure, improves with each release, is supported globally, and has a growing list of ISP provider/hosts that recognize its' value. 

A consultant has to say something, I know this because I do consulting, but it doesn't make consultants gods or fortunetellers.   A good consultant will back up their report with facts, not generalities.  Don't be dismayed or led to believe your work is anything less than the quality you give to it, and make sure you let your customer know that you stand by your choice of framework and technolgy.  Do some homework, compile of list of performance statistics and business that use DNN and host it.  Then, you can respond to what ever critique others throw at it. 

That's my opinion, and I'm not really a MS die-hard.  In fact, I'm back to using Unix and Linux because that's what the folks who pay me want, and it's really in support of a clininical information system not a web site. However, after working on DNN, and advocating its' adoption in house for 4 years, it appears that's we are going to finally move to using DNN for our web site. Of course, it helps that we are mainly an MS concentric site at this point. 

 
New Post
3/28/2008 10:08 AM
 

Hi Mike,

I'll agree that it is a statement that you really don't need to have too much concern with as long as the site you have built really is as fast as most other dynamic sites out there. 
However, I don't think it'll be too easy or good for your business to tell a high profile customer that their paid consultants have some other agenda and should not be listened to.

The fact is, ASP.Net is slower than PHP when you have two sites that are comparable in design and all the other aspects that need to be optimized regardless of language.

A classic ASP site is more comparable, because PHP and classic ASP are interpreted and not compiled "Just-In-Time". 
The JIT compile process happens way too often on an ASP.Net website to be able to overlook it.

DotNetNuke is also a Website Project that gets compiled on the server, so it'll be slower than another ASP.Net CMS that is pre-compiled before being deployed.

There are some very good arguments in favor of DotNetNuke that do not involve speed, so I think the best thing you can do is to get past the speed issue by optimizing the site as much as possible.

If you have not used YSlow for Firebug a FireFox plug-in, I highly recommend getting it and performing as many of the optimization tips as you can.

Also take a look at my Free PageBlaster module for increasing ASP.Net Performance. I also have a new version of PageBlaster that does several of the optimizations recommended by YSlow automatically that will be released very soon.


DotNetNuke Modules from Snapsis.com
 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Website Critique condemns the use of ASPWebsite Critique condemns the use of ASP


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out