JSP

[Guest]

He He He
Microsoft just has copied JSP technology...
But there is a big difference between ASP.NET and JSP:
ASP.NET is full of bug product and Visual Studio is an unreliable IDE.
See JSP technology to know.

I'm so sorry for myself that have waste my time with Microsoft's technologies.

I'm telling this as a .NET expert that has more than 10 project experiences
with ASP.NET and C#.

Switch to Java and J2EE solutions as soon as possible to enjoy your
programming life.

 

[Eliyahu Goldin]

Sorry for your wasted time and wish you great success with another
technology.

Good bye.

Eliyahu

 

[Flip]

Switch to Java and J2EE solutions as soon as possible to enjoy your
He He He
I actually have the exact opposite opinion of your conclusion. I am coming
from a large j2ee project where we had to create what .NET gives you for
free! I had to learn/install/support multiple OS' (linux is a very
troubling and has it's own set of deployment issues different from it's
sibling :<). As for the IDE, if you're used to JBuilder, then ya, I agree,
VS has some learning to do, but it's not THAT bad. What I found worse was
Borland's six month release cycle for JBuilder over the past four years!
That's bad when you have to pay 5Gs very version for your IDE. :< AND on
top of that, it didn't always work either. I'm using JB2k5 right now and I
can systematically bring JB to it's knees while debugging JSPs, EJBs under
WebLogic and JB. :<

And here's the kicker, what I can't do in a week (evenings mind you) with
j2ee I did in one night with .NET. Installed two OS (patches included),
RDBMS' with database, users, security and libraries, install the IDE (yup,
and patches), and the required libraries/packages, created and deployed a
web app which queries that news created DB/tables and updates them and lets
you view those updates.

Hey, maybe I'm a windows guys, that's probably true, but productivity seems
like the second priority behind .NET. Unfortunately it wasn't even on the
radar for j2ee. :<

 

[Guest]

Dear Flip
Thanks a lot for your answer.

Yes, I know about the productivity power of .NET Framework.
But I know about many bugs and problems in .NET Framework that make large
risks for your project, too.

For Example, I had a big project 1 year ago. In middle of production phase,
we faced a very big problem with ASP.NET web controls. We sent an e-mail to
Microsoft support team and they just replied "wait for next .NET Framework's
service pack".

What do you think about this? A famus problem in most popular Framework..
I don't say that it must be perfect. But this is not new issue in Microsoft.
You see this problem in all Microsoft's products.

I can just say **** of Microsoft. Down with Microsoft....

Good luck