From my last presentation in college:
In terms of coding, it's always just preference. Code what your boss tells you to code.
As far as server side, jsp/servlets are fastest following certain rules like you have to be executing from java byte code and you have to have enough concurrent processes running to outweigh the cost of loading the entire engine into the system at once. if you're only going to have 1-2 users at a time accessing the jsp, php is a tad faster.
php, for the most part, is faster than asp, though a few exceptions do exist.
ASP is the most flexible code, however, in that you can specify multiple interpreters, each taking slightly different amounts of overhead but you have incompatibility issues on unix based systems. It also seems to be the fastest option when using a windows based host as opposed to using a port of php or jsp to windows.
perl is the fastest bar none in single requests, but the overhead you incur when you have many simultaneous requests hitting the server is dramatic and is totally dependent on how good the kernel is at creating and destroying processes as opposed to the actual script interpreter.
As you can see, it's really just pick the technology that fits your need. On a windows host, it looks like you'd want asp. On a unix host, it looks as if you want to avoid asp. For small numbers of requests or if execution time is particularly important as opposed to initial response time(like on an intranet), perl is good. php seems to be the general winner overall. JSP/Java is preferred on systems expecting large numbers of requests.
A few extra things:
Windows hosts are generally more expensive, I imagine, because of licensing issues with IIS and/or the general difficulties associated with bringing unix native programs to the windows platform like perl or apache and their maintenance and I think that the unix kernels are somewhat faster, but have no evidence to support this.
JSPs seem to be the language of choice for designers(as opposed to coders) as a jsp can be done as html with static calls to code that the designer never has to know about. ASP also has this ability with codebehind. You can kind of do it with php using includes, but that presents a security risk sometimes.
All the above is also subject to human error. IE, a very poorly implemented perl setup will have longer execution time than any of the other technologies despite the efficiency of the interpreter.
We got a 'A' on this presentation, so I assume we weren't completely off our rockers.
In terms of my hyper-biased, opinionated view, php is better than asp.
... I think, could be that he meant that linux based is Red Hat, Caldera, Slackware and so on, who knows? dont even know why I'm trying to guess
Facebook
Twitter