My two cents on this issue:
For most average sites, Both these tools work well and the speed isn't the
issue but rather your shops expertise and style that really decide which is
the better product. I have to smile since in these enviroments its not the
programming language that is to blame for bad performance but badly
programed code that kills the project or response time. So pick the
programming language that matches your shops programming style. If you are a
cookie cutter style shop then ASP is your tool, its great for cut and paste
coding. IF you have a strong object based shop then JSP will rock over ASP.
But it really comes down to style.
When speed and size are the main issues then based upon platform
requirements you can choose the approriate solution (jsp vs asp) Both asp
and jsp can be made to rock the world, but in each case its when your
plaform is tuned to match the solution. So its still a style issue, a style
of hardware that your shop excels in. Pick the solution that matches your
shops style yet again.
So from my point of view both JSP and ASP are great solutions as long as you
use them in the right enviroment and programming staff.
I have to admit my bias's, I just love JSP, it is just plain fun to program
in a good object oriented enviroment, Plus it offers wonderful solutions. If
I had to choose one I would choose JSP but on saying that
I will also admit for the next year to come JSP will always be playing catch
up with ASP.
This is due to two reasons.
1) ASP is just easier to learn (ok JSP is easy to learn , but to really
unlease the power of JSP, you also need to know Java and you should
understand Servlets and JDBC and these 3 extra burdens make the JSP learning
curve a much steeper one. Add on top this JSP is newer and the educational
materials are still in mid stages of chaos, but with a smile I can say this
is finally turning around)
2)The ADO object and the ease of using stable ODBC connections. In my
opinion JDBC is easily a year behind the functionality and ease of use of
the ADO Data connectivity enviroment. And its these two issues that
ultimately which will keep JSP behind ASP in the numbers.
Casey Kochmer
www.JspInsider.com
[EMAIL PROTECTED]
>From: Gerardo & Liza Recinto <[EMAIL PROTECTED]>
>Reply-To: A mailing list about Java Server Pages specification and
> reference <[EMAIL PROTECTED]>
>To: [EMAIL PROTECTED]
>Subject: Re: FTP From JSP
>Date: Fri, 7 Jul 2000 22:31:56 -0700
>
>Let's explore more on a related topic as I like this {:))..
>
>I still can't figure out why the sentiment against MS when that it is doing
>a good job bringing out high performance softwares ? {:(
>(I am also not an avid MS fan although I worked under Bill's army of
>software developers. 'got to stay neutral to survive in this competitive
>world {:)
>
>Maybe, so many people failed to adopt/learn C++ nor liked basic for its
>unelegenceness (both are extremes) that they need something easier but
>elegant to work with and then somebody who is fed up with C++'s short
>comings when he is working for this networked devices' project came up with
>a simpler to use (but of course with performance trade-offs) and more
>adapted to internet programming that is now the famed, the holy grail, the
>numero uno ballerina of programming world, JAVA.
>
>Or, is it due to MS' competitor SM's successful advertisement of JAVA that
>lured away programmers from C++'s/VB's world. And then, naturally, all JAVA
>related technologies, environment get to be embraced by the whole
>programming community (or at least all the noisy ones who are not pro-MS).
>
>Or rather, JAVA is the next natural evolution of C++ programming language
>and that it was embraced right away by developers who saw all the
>advantages
>of JAVA as vs. C++ (not to mention basic since it doesn't rise up to the
>elegance level {:).
>
>But indeed, how can a JAVA compiled to bytecode (that needs an interpreter
>or a runtime engine) compete with the speed of a native, compiled to
>machine
>code COMponent. But JAVA is a language, therefore, it is not hopeless that
>someday a compiler + JAVA runtime engine can match up with the performance
>of a COM. But never to be better in performance, only in built-in features
>and in simplicity.
>
>Hardware performance, they say, will compensate for a software speed
>inferiority. As such, it is better to have a more tamed development
>environment rather than to have a better performing software dev.
>tools/enviro. In this case, if JAVA is the next evolution of C++,
>therefore,
>given a better tamed JAVA environment means it is a better option to
>choose.
>But then again everything is relative. That's why SDE's are always the
>heart
>and sole of a software dev't project, they are the ones who design &
>optimize the software. No matter how good the features are if the engine is
>slow and poorly architected, it will be a slow poke of a software.
>
>A comparison study of the 2 camps' technologies:
>MS:
> - Basic++ (next release of basic WILL formally raise it up to an
>OO
>language) for ordinary scripting/coding requirements.
> - C++ for extremely high performance needs.
>
>SM:
> - JAVA for anything under the sun (server side beans, servlets,
>JSP and
>client side applets components). Will continously be optimized to gain
>better performance.
>
>Bottom line is, MS has promised better OO language features to its
>unelegant
>Basic and better tools for easier C++ dev't whereas SM (and other JAVA
>software companies) has promised (or rather, focused on) better performance
>but currently has the edge in language features.
>
>We can't get the best of everything, for now, we have to settle up. My only
>real solution in this kind of dilema is my conceptualized language neutral
>interpreter/compiler. But it is never in the works as I am not hired to do
>such. I can only conceptualize as time doesn't permit more. Basically, we
>need to end this languagecism by introducing a compiler that when fed a
>grammar, will compile and optimize for that grammar's embodied language. OS
>API or native services (and highly optimized native runtime executive if
>needed) + this compiler is the winning combination. THis is the future,
>when
>this will be realized I don't know of..
>
>But then again, just like what I said, we have to settle up and choose one
>for now.
>
>-gerardo
>
>-----Original Message-----
>From: A mailing list about Java Server Pages specification and reference
>[mailto:[EMAIL PROTECTED]]On Behalf Of Shrisha Radhakrishna
>Sent: Friday, July 07, 2000 8:09 PM
>To: [EMAIL PROTECTED]
>Subject: Re: FTP From JSP
>
>
>I have developed 7 projects with ASP/COM and I have to say that this
>combination certainly outperforms the JSP/EJB/Servlet design I am currently
>working with.
>
>--Shrisha
>
________________________________________________________________________
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com
===========================================================================
To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST".
Some relevant FAQs on JSP/Servlets can be found at:
http://java.sun.com/products/jsp/faq.html
http://www.esperanto.org.nz/jsp/jspfaq.html
http://www.jguru.com/jguru/faq/faqpage.jsp?name=JSP
http://www.jguru.com/jguru/faq/faqpage.jsp?name=Servlets
