PHP vs JSP vs ASP vs PERL

Anon

i want know the advantages of PHP
over Perl,ASP and jsp. Is php multithreading.
which is the fastest.
why i should prefer php over other three.
thanks in advance

Anon

I mess with .jsp at the office -- VERY expensive, and you won't get the most from it unless you are up to speed in Java. Hard to learn, messy error handling.

M$.asp -- VERY expen$ive.

Perl, maybe it's just me, but I struggle with the learning curve. Not HTML-embedded.

PHP, EASY to learn. NO cost. Growing like a weed. Good support in various forums. As opposed to Perl, written for the web. Built in support for all viable DBMSes. Built-in functions for network, WDDX, XML, SNMP, PDF, LDAP, etc., etc., and now sessions.

I am a big fan of PHP. As to what's fastest, of course that depends on the application, the database and the tightness of the code. I would be interested in what others have to say about this.

Anon

I totally agree with Peter : PHP is very easy to learn and does not cost anything. I'm very surprised how easy and quick it is to implement the features I want in my web pages.

When starting using PHP, I was worried about the documentation and help I would find about it. Now, I'm not anymore at all ! You can find many forums, mailing list, etc.

I'm using MySQL and I'm very happy with the native access to it.

One word : excellent !

Anon

I can't disagree that PHP is very easy to learn and implement,
and it's usually my first choice for rapid implementation of a web-based application.

However, if the application needs to be speedy and robust, I'm more likely to choose Perl, just because Perl still has some tricks up its' sleeve that PHP has yet to learn.

THIS IS NOT PERL ADVOCACY! I use, and really like, BOTH languages. They both have their places and best uses, that's all.

BTW, Perl can be embedded into HTML - hence the mod_perl Apache module. mod_perl tends to be more resource-hungry than mod_php, though....

Just my 2c.

Anon

I use java, php, perl but I must say that php is the most powerful and definately the most productive. Perl in my opinion should be avoided like the plague since the code is usually by it's syntax un-maintainable. I have to build apps that others can maintain so therefore php is the tool of choice.

Anon

I've programmed in all of the languages above and have fallen madly in love with perl.
It quick, easy, fast and extremely useful.
Whatever you might ever need to do, there is a module that helps you get the job done. ANY job at all.
There is no task I have come across in web development that I couldn't solve writing a perl script.
For some reason people keep talking about PHP as being easier to learn than perl, I really didn't find perl hard to cope with (at least in a very basic level).

Anon

Which reminds me of another couple of reasons perl sucks. There is a module for everything and it makes moving code to another server a real pia. You have to reinstall all of the modules that are used in the original on the new server. To move a php app you just copy it over and bingo it just plain works. Perl was very difficult for me to learn also since the syntax makes absolutely no sense to a traditional programmer.

Anon

I think that you may be looking at the capabilities of these languages in a very limited manner.

PHP can in no way be considered the most powerful of these languages. It's far behind Java and even Perl as far as capabilities go - still more of a scripting language than a full-fledged programming language.

Perl's readability is, like any other language, dependent upon the programmer. I can show you some PHP code from one of my designers, and you can barely read it...

As far as portability goes... how portable is a script written in PHP that relies on the use of flock(), or semaphores? Portability isn't determined by something as trivial as modules, it's determined by the conventions and structure employed by the programmer.

Anon

Hi, check out this link to know more about the problems of JSP -
http://www.servlets.com/soapbox/problems-jsp.html

Though JSP does not seem 'efficient' to code, I'm not so sure abt Servlets and EJB. It seems quite a good idea to be able to package your code into "components" like Beans. I am starting to learn them now (no choice; Java programming is much much more in demand here compared to PHP or PERL😉). But nothing can beat PHP in terms of simplicity, elegance, etc.

regards,
jonathan

Anon

All of you have given comparison between easeness of coding and simplicity.
Its true that php and perl are the most easy to learn and code but i want to know if
same program is written in php,asp,jsp and perl
which will be more faster.

Is php supports multithreading like jsp?

As today's trend is toward java.There are very rare jobs in php in market.

There is something that programmers are preffering JSP over PHP.

Anon

Is php supports multithreading like jsp?

As today's trend is toward java.There are very rare jobs in php in market.

There is something that programmers are preffering JSP over PHP.

Anon

Is php supports multithreading like jsp?

As today's trend is toward java.There are very rare jobs in php in market.

There is something that programmers are preffering JSP over PHP.

Anon

gogi wrote:

I'm curious too. Why don't you tried them out? i think it also depends on your operating system and your hardware. For me, php on linux/apache is a speed demon, even on a low-end PPro machine(well, everyone knows how stable and fast linux is). ASP on IIS can be fast too if i'm not wrong, but the hardware requirement is usually much higher.

As for Java, a lot of ppl has been complaining how slow it is...there's the 'volano' report where you can find out the difference in performance between various JDKs and Servlet Engines.

But i agree with you that nowadays due to the hype of 'Java', everyone is either doing Servlets/JSP or EJB(i have to face this 'harsh' reality from the job interviews i have been to so far). So, if you are working for a cash-strapped start-up, PHP or Python/Zope would be the best choice. But if you are in an established company (where a few thousand dollars is nothing to them), you have more choices, i guess.

regards,
jonathan

Anon

JSP - gotta know Java!

ASP - ...nod difficult to learn but...

PERL - Lots of fun but somewhat tedious

   learning!

PHP - Lots of fun! Easy to learn! Overall,

  less costly.

Anon

dear friends,
I worked with perl .. and don't know much abt ASP or PHP .. But finally i am settled down in JSP.
JSP is the cutting edge technology.
It has got many good features.
we can't write big and complicated programs using PERL as it is loosely typed.we don't have multithreading programming(for good scalability) in any of these except JSP.
we have persistent database connectivity, database connection pooling,custom tag development , separation b/n presentation logic and business logic , good security with JSP.
USing JSP you can develop the code easily and maitenance is easier . JSP is good in all the above aspects.. just check out whether other programming langs support all these or not ..

have fun,
A friend.

Anon

I suggest that anyone who complains about having to learn something not expect a long lived and exciting career in the computing industry.

I know PHP is very powerful and very quick. I also see the direction of PHP being influenced by the capabilites of Java. I.e., PHP seems to be getting more "Java like". I see OO capabilites are growing in to PHP, which simply leaves room for some of the same mistakes that can be made in C++ that gave rise to Java in the first place, mainly the mixing of structured code and OO code.

JSP is meant as an access point for Java functionality for web pages. It allows the server side folks to develop robust applications (tha can work in higly scalable systems such as application servers using EJBs) that can be accessed by the web programmer from a simple JSP tag. To get the most out of this, it often means that the HTML person has no clue what the java code actually does. The beauty is, they don't have to.

So the problem is which aspects should you compare, and what is YOUR need? Are you making a small to medium size site on your own? Or are you managing an enterprise level system with web access that is being developed by a team of over 30 developers???

If you say the former, then I would say don't waste your time or clutter up your resume with things like Java. You can be happily employed out of your spare bedroom for a long time. If you are looking into the latter, then the Java model is your ticket. I don't even think of MS ASPs as an optiong, because I like my systems to run on stable platforms. But that's just a personal preference. 🙂

Make sure you are comparing apples to apples.

Chris

Anon

Yes, but...

My overall concern in all this talk about scalability and ease of learning, speed... is stability. We use Apache and to run JSP here, we needed to implement Tomcat. We haven't gone live with this, just using it on our dev server.

The fact that Tomcat gets hosed up scares me, despite the multithreading. I'm afraid that once we put our corporate site on it, and run jsp pages, Tomcat will be going down often. (unacceptable)

So the real issue for me, knowing all the above languages pretty well, except for ASP, is stability.

Is anyone out there using jsp on their server, and if it's getting lots of hits, does Tomcat stay up well for you?

Cheers,
Richard

Anon

A local web-dev company has been using the Apache-Tomcat combo for a while now. Most of their existing work has been trad Perl/cgi, but they are doing most of the new stuff with servlets/jsp. The don't particularly have hi-traffic sites, but they do have many sites being hosted by the same server. To my knowledge, Tomcat has never brought the system down.

Some other points: Tomcat is good, and it is free, but it is a pain to maintain and configure. Getting it to work and getting it to work WELL are two very different things. And administration? Granted, it is like a lot of Unix type systems and needs little maintainence once set up, but if it does, you REALLY need to know it well. But you can't beat the price. If you have the resources, I highly recommend JRun Server Professional. It can be installed to run with Apache on a Linux box in about 10 minutes. I has web based admin. I also has a lot of cool features like maintaining DataSource objects (pooled database connections in a naming service). It has a free dev license if you want to play with it.

Basically though, if Tomcat is not stable or performing well, it's probably your fault.

As a side note, a friend of mine is a professional servlet developer. The front end, i.e., html is done in a seperate shop. She just hands them the jsp tags to use to get the dynamic content into their pages, and it makes for a very nice, clean separation. You CAN put all the java code in the JSP, like you do with ASP, but this way you don't have to worry about someone fat fingering the script that they pasted into their page.

chris

Anon

go to hell

Anon

if you are comparing php with the immature tomcat, obviously the results will be favorable toward php, especially since php is now on it's 4th revision (with the Zend engine) and has had years of programmer input, while tomcat is still new and has not yet added any optimizations yet.
However, if you go with commercial quality servlet/jsp engines obviously they can change this perception that java is slow. For example see the results for resin at http://www.caucho.com/articles/benchmark.html.
I think php has it's merits (such as a huge user base, helpful people, maturity, speed, numerous webhosting sites using it), but I wouldn't discount jsp if I were you. It might be in it's infancy right now, but the mighty marketing arm of Sun is going to make it the language de facto for Fortune 500 companies (if they get their wish). I also wouldn't discount Microsoft either with it's .NET and ASP+ offering. It's actually quite impressive.
I would like to see php beat these (it's free), but it's not going to happen if we just talk bad about the other scripting languages on an unfound basis. Instead we should see how we can improve php (ie modularization, DB pooling, unified DB interface, ease of extending php, etc).

just my 2 cents