J#
fuze writes: "It's basically a way for Java developers to migrate their Java apps to .NET.... even provide a 'convenient' migration tool... check it out on MSDN." News.com has a story describing Microsoft's plans to suck Java into .Net, and some commentary saying basically, "No one will use it".
In short
This is Flame Bait and I am a Troll, Please moderate accordingly.
Fascism should more properly be called corporatism, since it is the merger of state and corporate power - Benito Mussoli
No matter what tools come on the scene...
.NET does provide some integration and improvements on all the tools you've been using. For one, C# is an easy language to program in and with the right JIT/processor match it can be as fast or faster than C/C++ compiled for non .NET platforms. It buys you a few other things as well like reference counting/garbage collection. MS provides a .NET C/C++ compiler if you want that. Nearly any other language with the right type structure can be compiled to the .NET VM, including one day Perl.
.NET. XML and HTTP support are built into .NET. HTML support is not, but you don't need to be writing code to sling HTML... ASPX does it for you very nicely. Ever write a Windows app and then with a few changes to the code have a equivalent HTML-based app?
.NET tools. You can keep doing what you're doing and be happy. But .NET is really set up to integrate alot of the things you do into a tighter package... 1-stop development if you will. If you want to have an easier time integrating the components you mention, you might consider .NET as an option.
That's fine, don't give them up. But
Database support is built into
There's nothing that says you need