Re: Why JSP is better than PHP >>

I'm going to go out on a limb here... Once you boil it all down to the core feature sets, all the major scripting languages (PHP, JSP, Perl, CF, ASP) are all about the same, each one has it's own set of advantages and disadvantages. Here's my take on it.... If: 1) You can build your application more quickly in one language than in another 2) You can write the code so it'll last more than a year and can be handed down to another developer 3) It can scale to your needs.... not everyone needs a $19,000/month Exodus connection with racks and racks of servers 4) You can afford the cost of the license Then use that language. If your language can't meet these conditions, look at one of the other ones. PHP can handle these conditions for me, yet, so can JSP, and ASP and CF and Perl, some make it easier/faster to code in than others, some scale with less $ than others, some are more easily expandable than others, and hell, some are just more fun to program in than others. Screw what others say, use the language that's best for you. Steve Nelson http://www.SecretAgents.com Tools for Fusebox Developers Erick Papadakis wrote: > > Forgive me for a rehashed topic but the following has > been thrust into my face by a guy who was born with > Java skills and is still using the bloatware - > > ----------------- > Here is a list of reasons why JSP is better than PHP: > > 1. Anything you can do with PHP, you can do with JSP; > the reverse is not true > > 2. JSP is much more powerful, since it has access to > all the Java libraries. PHP only has access to PHP > libraries > > 3. JSP is Object-Oriented, so leads to cleaner code > that's easier to debug, maintain, and improve. (PHP > also allows objects, but the object model is more > primitive, and most scripted pages ignore PHP objects > and just use normal variables.) > > 4. The equivalent syntax in JSP is just as simple to > learn, so you can get up and running just as quickly > -- that is, there's no extra startup cost in using > Java, at least not a significant one > > 5. Java programmers (as opposed to 15-year-old hackers > or HTML monkeys) appreciate the importance of a clean > language with complex OO data structures and strong > typing > > 6. With JSP, if the code inside a page gets too big, > or if you want to use it elsewhere, you can cut it > out, make it into a Java class, and invoke it from > anywhere in your application (even not from a page). > With PHP, you're stuck inside the HTML box. > > 7. JSP's concept of state management and persistence > is more explicit and powerful than PHP's. With JSP, > you can specify whether a variable persists for the > page, the request, the session, or the application (or > if it's just local to the function). The JSP engine > automatically does the right thing with cookies so you > have access to the variable on later requests. With > PHP, you just have "global" and "not global", you > don't have automatic session management, and have to > do your state thing manually with cookies or hidden > variables. > > ----------- > > Please help! How can I talk back? I would appreciate > any guidelines and advice. > > Cheers/erick > > __________________________________________________ > Do You Yahoo!? > Yahoo! Calendar - Get organized for the holidays! > http://calendar.yahoo.com/ > > -- > PHP General Mailing List (http://www.php.net/) > To unsubscribe, e-mail: php-general-unsubscribe@lists.php.net > For additional commands, e-mail: php-general-help@lists.php.net > To contact the list administrators, e-mail: php-list-admin@lists.php.net --