ASP V PHP v ASP.NET V CF V JSP

[DigitalBuilder]

ASP V3 [Classic]
-Server Loads may be greater because of trying to improve income to expensive server
-Includes may be processed for the whole page rather than 'as needed' making it slower
-Uploads can be done but may be limited
-Image resizing may require pay or free components that may not be standardised between servers.
-Higher price Hosting
-Access Not good bigger envirvonments
-MSSQL Expensive
-Compiled may be 3rd party addon

PHP
+Low Load / cheaper servers potentially
+Includes as needed [Unless someone wants to correct me here?]
-/+ Uploads similar
+Graphics facility with PHP support which allows thumbnailing
+High Server Amount
+Cheap Hosting
+MySQL Fairly Cheap, medium load ability or so
-Compiled may be 3rd party addon
+Common in New Zealand, currently most common in this regard?
+Industry stats may suggest very common in 1-5k project mark

ASP.NET
-Proper tools expensive
+Free Options
+Can be compiled natively
-Expensive servers for pro choice

ColdFusion
-High Server Cost
+Very Fast to code
-Common but not that common

JavaServerPages
+May be more powerful langauge
-May not be native
+Makes 70% of 1 million dollar plus projects
-Not common for small end

Not the be all and end all, what would you add?

 

[trollacious]

What's available to you NOW? What do your clients need NOW? Comparisons and wish lists are nice for theories and hypothesizing. Learning a variety of things is good, but you won't retain what you learn as well if you don't actually use it, and you won't get REAL experience unless you have real life projects to apply your knowledge to.

I use classic ASP and PHP because that's what my clients need. Those 2 cover what the vast majority of web hosts offer.

Lee

 

[BabyJeffy]

Regards ASP...
+ works with mySQL (providing a free, production database solution)
- single platform solution (since Chillisoft ASP is not exactly the same as IIS ASP)
- can't use .htaccess properly (as in - fully) with windows

I don't like that you have a lot of "may" statements. For instance you say:

Uploads can be done but may be limited

And yet you don't provide any background to support your statement! I have implemented ASP file upload solutions in the past and they were fine for everything that was needed. So what do you mean by "may be limited"?

Regards JSP...
+ works on any platform/os combination (that has Java)
+ communicates to every database
+ allows full extension of a web app through servelet and bean use
+ is available in a free version (Tomcat)

I think your post is a good starting point and could very well become a useful comparison/justification for choosing one over another for a particular project... but you need to define the boundaries a little more and backup any perceived "negatives" with justification/proof/etc (and compare like with like). Maybe generate a set of benchmark statements that hold true for all/most as well.

It's interesting that you talked about NZ in there... are you referring to NZ dollars when you talk about cost? Just curious.

Cheers,
Jeff

 

[DRJ478]

To me it seems more like the question will be:
Are you going to go the commercial/proprietary route (ASP etc.) or be with the open source community (PHP/MySQL etc.).

Not mentioned at all is that PHP is platform agnostic (just like Java with the appropriate JRE).

PHP code can be encoded (Zend Encoder, Turck mmCache), to be used on any system that has Zend Optimizer or Turck mmCache. There is also a product that generates stand alone PHP applications (most people probably never heard about that):

http://www.roadsend.com/home/index.php?SMC=1&pageID=compiler