.NET advantage over JAVA
-
Hi everyone. I'm developer on .NET platform, but I never was intrested in Java. Can you tell me any advantages .NET over JAVA? Or some advantage JAVA over .NET? Thank you in advance!
Here's how I see it, as somebody who uses Java and .NET every day: .NET ADVANTAGES --------------- 1) Good to great integration with Windows, Active Directory, and other Microsoft products and services 2) Ease of integration with C++ code (in Java you must use JNI, not much fun) 3) The C# language is a little cleaner than Java and provides better support for OO development, with properties and a richer set of keywords. (A few things can actually subvert good OO design, like method hiding, but you don't have to use those features.) The language is more suitable for lower-level work than Java, while still providing all the features of garbage collection, multiple-platform deployment, etc. 4) The marketing muscle of Microsoft, nothing to sneeze at, means you'll be looking at green pastures for a while. Microsoft is also committed to supporting .NET for the foreseeable future, and has based much of their corporate strategy on it going forward. 5) The .NET runtime is better optimized for some things; object creation is less expensive in general, method-call overhead is a little less, etc. 6) The CodeDom namespace simplifies the task of dynamic code generation, something not supported in the Java core libraries 7) Excellent, excellent free documentation on everything you may want to do in .NET, with further support through the usually-excellent Microsoft Press books as well as authors of third-party publications (our own Nish and Tom Archer being a good case in point) 8) Ease of deployment for Web services is still far better than anything you'll see from a third-party Java tool IMHO, although I haven't seen the latest versions of Websphere Studio and BEA's tools 9) ASP.NET is better suited to RAD for presentation purposes. I'm sorry, JSP fans, but it's true; I know from experience. 10) Microsoft-centric developers are a little less likely to spend four hours a day at the water cooler engaging in object-oriented oneupsmanship. ABOUT EQUAL ----------- All in all, it seems to me that they're about equal in terms of what's provided in their base libraries. Their security models are equally powerful and extensible, although with .NET you'll find it easier to work with Active Directory than othwerwise, no surprise there. Runtime speed of code is about the same in my experience, although I'd bet that calling native code on Windows works faster in .NET than in Java. They both have open specifications. They both have support for embedded code and small devices, with .NET support
-
Here's how I see it, as somebody who uses Java and .NET every day: .NET ADVANTAGES --------------- 1) Good to great integration with Windows, Active Directory, and other Microsoft products and services 2) Ease of integration with C++ code (in Java you must use JNI, not much fun) 3) The C# language is a little cleaner than Java and provides better support for OO development, with properties and a richer set of keywords. (A few things can actually subvert good OO design, like method hiding, but you don't have to use those features.) The language is more suitable for lower-level work than Java, while still providing all the features of garbage collection, multiple-platform deployment, etc. 4) The marketing muscle of Microsoft, nothing to sneeze at, means you'll be looking at green pastures for a while. Microsoft is also committed to supporting .NET for the foreseeable future, and has based much of their corporate strategy on it going forward. 5) The .NET runtime is better optimized for some things; object creation is less expensive in general, method-call overhead is a little less, etc. 6) The CodeDom namespace simplifies the task of dynamic code generation, something not supported in the Java core libraries 7) Excellent, excellent free documentation on everything you may want to do in .NET, with further support through the usually-excellent Microsoft Press books as well as authors of third-party publications (our own Nish and Tom Archer being a good case in point) 8) Ease of deployment for Web services is still far better than anything you'll see from a third-party Java tool IMHO, although I haven't seen the latest versions of Websphere Studio and BEA's tools 9) ASP.NET is better suited to RAD for presentation purposes. I'm sorry, JSP fans, but it's true; I know from experience. 10) Microsoft-centric developers are a little less likely to spend four hours a day at the water cooler engaging in object-oriented oneupsmanship. ABOUT EQUAL ----------- All in all, it seems to me that they're about equal in terms of what's provided in their base libraries. Their security models are equally powerful and extensible, although with .NET you'll find it easier to work with Active Directory than othwerwise, no surprise there. Runtime speed of code is about the same in my experience, although I'd bet that calling native code on Windows works faster in .NET than in Java. They both have open specifications. They both have support for embedded code and small devices, with .NET support
-
Thank you Jeff! Your message is very useful. If I can ask, what do you think, JAVA+Linux==.NET+Windows? Thank you again!
They're both viable platforms. A lot of it has to do with the specific situation. I have a lot of experience with Java, and I used to have a lot of animosity towards Microsoft as a company just because of the company I kept, but that's dwindling all the time and not something on which to base a purchasing decision. If you have a lot of Microsoft technology, .NET is the way to go, hands down. If you need to deploy mission-critical application on Unix, you have to go with C++ or Java. I tend to think that Microsoft technology is better in general for small-to-medium-sized companies because it's very easy to learn, and productivity is easy to achieve. Like I said before, the RAD features of ASP.NET are currently unmatched; it seems to me that most of the in-house development needs for small-to-medium-sized companies are for database-driven Web applications, in particular reporting and intranet applications. Also, you won't get me to advocate buying into Java on this site, but I won't slam it either. You have to make your own decision! Of course, you can always migrate your Java code to .NET; I have first-hand knowledge that the Microsoft-provided migration tools work well enough. On the other hand, it's not so easy to migrate .NET code to Java, but it can also be done, and you'll probably never need to do it. -Jeff here, bloggy bloggy
-
Here's how I see it, as somebody who uses Java and .NET every day: .NET ADVANTAGES --------------- 1) Good to great integration with Windows, Active Directory, and other Microsoft products and services 2) Ease of integration with C++ code (in Java you must use JNI, not much fun) 3) The C# language is a little cleaner than Java and provides better support for OO development, with properties and a richer set of keywords. (A few things can actually subvert good OO design, like method hiding, but you don't have to use those features.) The language is more suitable for lower-level work than Java, while still providing all the features of garbage collection, multiple-platform deployment, etc. 4) The marketing muscle of Microsoft, nothing to sneeze at, means you'll be looking at green pastures for a while. Microsoft is also committed to supporting .NET for the foreseeable future, and has based much of their corporate strategy on it going forward. 5) The .NET runtime is better optimized for some things; object creation is less expensive in general, method-call overhead is a little less, etc. 6) The CodeDom namespace simplifies the task of dynamic code generation, something not supported in the Java core libraries 7) Excellent, excellent free documentation on everything you may want to do in .NET, with further support through the usually-excellent Microsoft Press books as well as authors of third-party publications (our own Nish and Tom Archer being a good case in point) 8) Ease of deployment for Web services is still far better than anything you'll see from a third-party Java tool IMHO, although I haven't seen the latest versions of Websphere Studio and BEA's tools 9) ASP.NET is better suited to RAD for presentation purposes. I'm sorry, JSP fans, but it's true; I know from experience. 10) Microsoft-centric developers are a little less likely to spend four hours a day at the water cooler engaging in object-oriented oneupsmanship. ABOUT EQUAL ----------- All in all, it seems to me that they're about equal in terms of what's provided in their base libraries. Their security models are equally powerful and extensible, although with .NET you'll find it easier to work with Active Directory than othwerwise, no surprise there. Runtime speed of code is about the same in my experience, although I'd bet that calling native code on Windows works faster in .NET than in Java. They both have open specifications. They both have support for embedded code and small devices, with .NET support
Hi Jeff. Nice summary. We had a pretty low cost entry into .NET -- most of my first year's development with .NET came from the free .NET SDK download and a $30 text editor. It's not the funnest way to develop WinForm applications, but it was great for components and ASP.NET apps.
-
Hi Jeff. Nice summary. We had a pretty low cost entry into .NET -- most of my first year's development with .NET came from the free .NET SDK download and a $30 text editor. It's not the funnest way to develop WinForm applications, but it was great for components and ASP.NET apps.
-
Hi Jeff. Nice summary. We had a pretty low cost entry into .NET -- most of my first year's development with .NET came from the free .NET SDK download and a $30 text editor. It's not the funnest way to develop WinForm applications, but it was great for components and ASP.NET apps.
Thanks! I got started with my favorite editor and the command line, then started using SharpDevelop, then got VS .NET as part of our MSDN subscription at work, so I identify with you. I was perfectly happy working on the command line for a while; it meant that I didn't get bogged down learning how to use an unfamiliar IDE. I'm sort of a Luddite when it comes to this stuff-- I don't even use the .NET debugger, ever. I just use
Console.WriteLine(), and haven't found a problem yet that I couldn't tackle with that! (I'm not knocking IDEs-- they get to be necessary just to manage files and class hierarchies as things get more complicated, of course.) -Jeff here, bloggy bloggy -
Yes, it's really decent in my opinion. I also know people who've used WebMatrix and say it's pretty nice, although it doesn't have support for everything. -Jeff here, bloggy bloggy