When we are browsing the internet nowadays, we can see a lot more websites are developed in ASP than in JSP. It seems ASP is much more popular than JSP now. Anybody know the reason why? What could be the trend for the future, ASP or JSP?
There are those who contend that statistics are what you want to make of them -- that there aren't that many Microsoft-based web sites, but the ones that are there are "big-name" ones. On a purely cynical note, I've heard it mentioned by one manager that VB programmers are a dime a dozen. Then there are the pundits that claim that Java is on the upswing, while VB is in decline. The usual justification is that Microsoft's tinkering with fundamental language constructs in its attempt to create VB.Net is making a lot of people nervous. Place your bets and take your choice. Or was it the other way around? [This message has been edited by Tim Holloway (edited July 17, 2001).]
An IDE is no substitute for an Intelligent Developer.
some considerations: 1)JSP is platform independent ASP not 2)JSP takes advantage of all the power of the java API while ASP VBSCRIPT OR JSCRIPT 3)JSP are compiled in Servlets and have a better performance than ASP. 4)JSP can use Custom tags and ASP(COM)???Whats that?? 5)JSP can use all the power of JDBC to connect to databases what if you design well can make your application DB independent. 6)Much more complient servers.
JSP technology is newer than ASP and there has simply been less time for it to be taken up. JSP is pre-compiled into servlets and then bytecode which gives it a potential performance advantage over ASP. I believe that ASP is parsed afresh each time. About 60% of all publicly visible web servers run the Apache web servers, approximatly zero percentage of them run ASP. Microsoft IIS runs about 30% of publicly visible web servers, you can make your own extrapolations and guesses at the overall percentage of sites that are running ASP. ASP is very attractive if you have an existing heavy commitment to VB and Microsoft technologies and you assume you are not going to be wildly successful (a safe bet for most web sites). Marcus ------------------ http://www.jchq.net Mock Exams, FAQ, Tutorial, Links, Book reviews ================================================= Almost as good as JavaRanch =================================================
Marcus, Your analysis is pretty much on the dot, and I have to agree with you completely. I'm a 'native' windows applications / systems developer and have been programming with VC++/VB for about 7 years now (even got my MCSD before getting the SCDJ). I looked at the trends in industry 2 years ago with the shift from core applications to web-based/web-centric systems and decided that I had to diversify career tracks before I fell into a rut. When you look at the massive support for the Java platform on all fronts ( development tools, operating systems, applications support, enterprise systems integration, application server support, training and certification, etc ) you cannot but see where the whole industry is going (imagine there's even a joint certification effort called jCert!!! supported by several vendors ...). I've never seen such a level of collaboration in our industry before. How many MS technologies can work on other operating systems integrated with other products and supported by other companies??? (need I say more?) Microsoft decided it was '..my way or the highway' when it decided to go it solo and stick to its guns. It would have been better for them to get 'a small (but significant) piece of a big pie' instead of the 'big piece of a small pie' its eventually going to end up with. The situation is very reminiscent of what IBM tried to do in the '80s and we all know how that ended. Because of all these coupled with the lack of direction which MS is exhibiting by throwing all kinds of divergent visions at its windows developers (yours truly inclusive) e.g ActiveX, COM, COM+, Microsoft.Net, C#, even the controversial VB.Net have made me decide to start hedging my bets and give MS some time to make up their minds before making any future MS investments. My company has also deciding to move some of its code base to Java. I must confess that though we're still doing over 70% stuff in VC++ we're more or less expecting this to change dramatically as time goes on and are very ready for it. Just my 2 cents worth. Akanimo.
hi, dont believe in statistics unless you faked them yourself.... while asp is parsed every hit, jsp is precompiled to bytecode. this seems to giv jsp an advantage. i posted on this a while ago. there are some stats....(remember: dont believe.....)
karl had my troubles with ubb
[This message has been edited by karl koch (edited July 18, 2001).]
I agree with Marcus that JSP technology is newer and therefore had less time to dissipate. I know of several companies, some of them household name companies, that are moving towards JSP technology. In fact, there are several that are moving from ASP to JSP. And this only makes sense considering that JSP is more robust than ASP.
This question is also like asking: I see a lot of sites using cgi rather than JSP and ASP. This is always due to the age of the programming language. After a while, once the trend kicks in, one programming language will dominate the rest. For a while, ASP was kicking butt and we see a lot more ASP sites due to the fact that there's been a LOT more time for ASP to commercialize and hit the market. There's few sites out there who use JSP but one thing I DO know for sure is that most of the sites, as mentioned before, are switching from ASP to JSP. ASP is NOT faster than JSP after JSP is compiled. The ONLY time I can think of where JSP is slower is when the JSP file is FIRST compiled. Other than that, it's pretty much lightning fast. I've also seen benchmarks where JSP outperforms ASP in some aspects (just as database connectivity) as more connections are made. ASP isn't as scalable as JSP and for this reason, more users are selecting JSP.
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com