dotNet vs J2EE

[Shayaan Siddiqui]

Hello

I am working on a new project and I would like to do it in dot Net

Can someone provide me with good irrefutable reasons to do it in dot net
than J2EE?

Shayaan

 

[Jon Skeet [C# MVP]]

I am working on a new project and I would like to do it in dot Net

Can someone provide me with good irrefutable reasons to do it in dot net
than J2EE?

Well, if you'd like to do it in .NET, presumably you already *have*
reasons, don't you?

Put it this way: what reasons are being presented to you for doing it
in J2EE?

There are various reasons for choosing one technology or the other, but
without more information it's hard to give any kind of balanced views.

Jon

 

[ArchitectOnTheEdge]

The reason why you would do a project in one technology or the other
should be cost related unless the project is free in that case its your
passion than anything else.

 

[William Stacey [MVP]]

Try it. You will never know for sure until you buid an app in .Net. Then
you will know.

--
William Stacey [MVP]

| Hello
|
| I am working on a new project and I would like to do it in dot Net
|
| Can someone provide me with good irrefutable reasons to do it in dot net
| than J2EE?
|
| Shayaan

 

[jeremiah johnson]

why is the application being created?
what are the requirements?
what advantages does it provide over current procedures/software?
what is the development time line?
in what language(s) are your developers fluent?
do you have appropriate j2ee hardware/software already?
do you have appropriate .net hardware/software already?
do you have the expertise in your administration to administrate them?
what is your organizations standard development platform, if any?

provide that kind of info, and we'll be able to help ya.

given what you've already said, no one can really fairly recommend one
over the other, but I can say from experience that j2ee and .net both
have their rightful place in the enterprise.

personally, i've been doing a lot of j2ee lately and it is hard to
resist the feeling that java solves every problem.

of course no single language solves every problem, but when your
favorite tool is a hammer, everything begins to look like a nail.

pick the right language for the job, not necessarily *your* favorite
language.

don't let your favorite language get in the way of the right decision.

jeremiah