As we know that now a days, different technologies for web application development are available such as Java and .NET. which technology is preferred over other technology and why?

Depends what you're doing. I'll always suggest C# but if you're wanting some sort of embedded client applet to run in a browser, go with Java.

What are you actually wanting to create though?? If it's a dynamic website I would suggest PHP.

I asked the qusetion in general which is better for web application development java or .NET?

Let me rephrase - Define "web application".

In-Browser Application? Java.
Dynamic Website? PHP.
Application that connects to a web service? C# (.NET).

This post has been edited by MageUK: 24 Jun, 2009 - 02:10 AM

VB.NET has always been my style. However, I don't really build web apps with it... I'm still a n00b to everything except basic HTML.

.NET, C# in particular: the IDE is exceptional and it has all the tools you could want. Deployment is relatively simple. IIS is the only serious option.

Java: IDEs are getting better, but you'll still be doing more code writing that drag and drop control manipulation. Runs on many servers, including it's own. Deployment can be painful, at least initially.

PHP: IDEs suck. More like old CGI web development. A ton of libraries, simple deployment, much more widely used on the internet than either of the prior options. LAMP stack in general is a defacto standard.

Ruby on Rails: Same IDE support as PHP; rudimentary, Eclipse seems to like it better. Rails is a well thought out MVC framework. Ruby is a neat language. Deployment is easy in house. Internet hosts are sparse.

Perl: Why not, almost any *nix based host will support it. Syntax can be a nightmare, but works.

Python: because all the big Open Source kids love their full monty. Another fun language to program in.

... there are many, many paths to web development. If you're a Microsoft shop, ASP.NET is the easy choice. For everyone else, AMP is the favorite. The simple fact is, web pages are mostly brain dead. If you can get a language to spit out HTML and consume HTTP requests, you have a web development language.

The real question is what kind of environment you're in, who your clients are, were you applications will be hosted, and what your skill set is.

Edit: oops, necro thread. Sorry.


This post has been edited by baavgai: 3 Jul, 2009 - 11:48 AM