RIIIIIIIGHT.
First thing's first: Language-wise (C# v. Java), C# was never finished b/c
Microsoft already had a significant market share. Java was developed to
beat M$ (primarily) and make developers happy (secondary). Additionally,
JSP was developed to copy ASP. JSP (taken from ATG Dynamo technology) was
then morphed into something new w/ the beans, servlets, teapots, coffee
filters, cocoa plants, and coffee machines. ASP+ is the natural progression
for Microsoft since its been in the works since '98. How? Well, ASP had
not really changed in spite of ASP3.0 being released a year or so ago.
Nothing was released because since ASP2.0 came out, it went into full-gear
for ASP+.
And when it comes to quality/speed/whatever, it all depends on the hardware.
No matter WHO YOU ARE, it comes to hardware. Java sucks on a P100 '95-built
IBM Aptiva running Linux... Anything Microsoft dated post-'95 sucks on the
box too... but with M$, we can put Win95, and hope for the best.
I own a P100 '95-built IBM Aptiva. I've tried.
Furthermost, and finally, YOUR CODE MUST BE CLEANEST, LEANEST, and
ERROR-HANDLING READY. Why the last? Because, in the real world, the more
shortcuts you take, the worse the program will be. The cleaner, leanest,
optimized, and error-handling the code, the better response time.
No more theoretical crap. It's time for the real deal... and
Java/JSP/Servlets/Teapots must "keep" ground before M$ takes it over.
Yours,
Nasser Dassi
Software & Internet Developer
[EMAIL PROTECTED]
"Openmindedness Rewards A Lifetime"
----- Original Message -----
From: "christopher brown" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, March 15, 2001 3:56 AM
Subject: Re: JSP vs. ASP+
ASP+ copies almost JSP identically.
When you modify a JSP page, the JSP engine compiles it into a servlet,
running under a JVM (Java Virtual Machine). Unless the JSP page is modified
again at some later time, future requests for the JSP page are directly
handled by compiled servlet.
ASP+ does the same thing. If you change the ASP+ script's source code, it
is recompiled. A compiled ASP+ script is not compiled directly into native
code for Windows (such as a DLL or EXE), but instead into "intermediate
language" ("IL"), which is more or less the same thing as Java bytecode (but
not compatible). This IL is executed by the .NET runtime (ASP+ is one part
of Microsoft's .NET strategy), in the same way as a JVM executes bytecode.
As for the number of languages supported by .NET, be careful... what they
really mean is that ASP+ can use scripts written in any language that has
been adapted / extended to support features of IL bytecode. Which is why
VB, MS JScript, etc. are being rewritten and/or extended to become
object-oriented, etc. One way to think of it is that each language says the
same thing, just phrasing it slightly differently. So don't expect any old
Perl script or COBOL program to run under .NET/ASP+... they must conform to
language features required by .NET.
Furthermore, with .NET, you're required -- or at least expected -- to use
certain APIs, such as ADO+ for data access. So, whether or not C# (for
example) becomes a standard or not is irrelevant... if C# was implemented
with Unix, it probably wouldn't have any access to Microsoft's proprietary
APIs, such as ADO+. As I said, I used C# as an example, but the same vendor
lock-in issues apply also to other key components of .NET.
Generally JSP is much better, as it can be implemented using cross-platform
APIs with any vendor (this has been a genuine advantage for me...).
Remember however that Java is still more or less proprietary technology
too... For the time being at least though, Sun are doing a good job,
evolving Java in the right directions...
-Christopher Brown
----- Original Message -----
From: "Mike Sankowitz" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, March 15, 2001 12:50 AM
Subject: jsp vs asp+
some guys from my company went to a m$ asp+ users group presentation here in
denver a couple of months ago. they were told that asp+ is compiled,
supports a bunch of different languages (like perl??), has built in support
for soap/xml, has some kind of page caching feature, has process recycling,
etc., etc.
also ...m$ is claiming that since asp+ is compiled it is faster than jsp
(yeah right, like vb is faster than java).
i've seen some material on jspinsider.com and i konw jsp has to be better
since it's written with java. has anyone else looked at asp+?
--Mike
_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com
===========================================================================
To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff
JSP-INTEREST".
For digest: mailto [EMAIL PROTECTED] with body: "set JSP-INTEREST
DIGEST".
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
===========================================================================
To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff
JSP-INTEREST".
For digest: mailto [EMAIL PROTECTED] with body: "set JSP-INTEREST
DIGEST".
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
===========================================================================
To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST".
For digest: mailto [EMAIL PROTECTED] with body: "set JSP-INTEREST DIGEST".
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
