Anonymous
Unregistered
|
|
I agree with most points. However, I believe Java will gain more client desktops as Linux becomes more widely adopted as a client plateform. While Java will gain some ground I'm doubt they will take over the Windows plateform. As one user stated windows is not the only desktop.
I'd also like to see Sun release the reigns of Java. Maybe offer up Java to ECMA as M$ did with .NET CLR and C#.
I'm also concerned with the "keeping up with joneses". I'd hate to see the Java go the way of C++ and become less intuitive and more cluggy.
Finally, "Java is the most mature and stable platform for enterprise computing available today. Microsoft is still spinning .Net, and it might eventually be as good or better than Java (but only on the Windows platform); right now, it's not."
I've particpated in design/developing large scale .NET (Server Based/N-tiered/Single Sign-On etc) applications in a clustered environment deployed on Windows 2K boxes as well as EJB(WebLogic/JSP) in a similar fashion on Sun boxes. Both apps handling transactions in the millions with(24x7 support). I can honestly say that in a 9 month period we did not have to reboot NO boxes. Our development tools included ANT, NANT, JUNIT and NUNIT etc. Coding standards/design patterns were almost identical/consistent in C# and Java. OS aside .NET has already made up ground and the "maturity" argurment is a joke.
Bottom line, Java is great, but so is .NET. While this article was not about .NET, the couple of comments made regarding it should be balanced with some founded experience and not religious fluff. NOTE: I'd say the same on a M$ related article if it bashed Java/J2EE.
I'm glad to see compitition. I not a M$ fan nor am I a Sun fan. However, I can appreciate what both bring to the table and I look forward to enjoying the fruits of this competitive joust. My two cents!
Long live Java!
I.D.C.
|
Humphrey Sheil
Unregistered
|
|
Hello Anonymous
addressing the points you raise:
>>OS aside .NET has already made up ground and the "maturity" argurment is a joke.
I'm disappointed that you think I bashed .NET in the article, however it's misleading to pre-qualify your remark with "OS aside". .NET is intrinsically married to the Windows platform - although initiatives such as Mono exist, .NET will always remain Microsoft's equivalent to J2EE and is for the Windows platform.
Realistically, J2EE is more battle-proven than .NET. There are many more times J2EE projects in production than .NET, simply by virtue of the fact that the J2EE platform has been around longer.
Microsoft will get .NET right - they have the resources to do it, but for example when you consider that there is still not a 64-bit .NET version available, we have to consider .NET to be less mature than J2EE - 64-bit JVMs have been available and battle-tested in production for years.
Regards
Humphrey
|
Anonymous
Unregistered
|
|
Hello Humphrey,
Point taken on the 64 bit issue. However, I would not say that "OS aside" is misleading. First, CLR, CLI and C# are all ECMA approved. It would useless for M$ to submit something that is Windows specific. Currently, I can write apps(Web or distributed components minus com+) that migrate over to Linux,HP-UX with no code changes.
I actually enjoy what Java/J2EE and C#/.NET have to offer. Neither are perfect but good. One problem I see with .NET is it's stigmatization to Windows. I could definitely see in the future where Java will make more head way on the desktop and .NET on the server. However, both are a ways off. As for Java, I really hate to see them mess up the syntax by "keeping up with the Joneses".
Great article!!
Terry
|
100permission
Unregistered
|
|
Can somebody tell me where i can find docs on Java vs .Net. as a beginer, i'm willing to know more about these tools.
Thnx a lot
|
turingcomplete
Unregistered
|
|
Your positive experience with .NET has been very differnt then at my work. From inexplicable application crashes ("Application not Found"), to buggy database drivers that don't close connections ("Maximum cursors exceeded"), to inexplicable runtime compiler failers ("Compiler failed..."), it's been an expensive ride. Compared with my previous experience with deploying similar apps in Java I would agree with the author that Java is more mature.
Add onto that the lack of checked exceptions which makes dealing smartly with exceptions impossible ("just let it go all the way up the call stack to the default error handler.."), and the way everything seems to be built with a "fail-supress" mindset, it's clear .NET was not made with mission-critical applications in mind. Instead MS is going for a different, simpler, market with .NET, and so will not be able to be the "perfect" platform.
|
Anonymous
Unregistered
|
|
How can one see Java on desktop after beeing times slower and inneficient than .net on the desktop (talking about Windows here) there are 3d engines build in .net performing near c++ siblings (Ogre3d-axiom3d) while all Java offspring in this area such hard in performance
|
Anonymous
Unregistered
|
|
do a research, make use of google.
Java 1.4 and java 1.5 is almost as fast as c++.
|
Anonymous
Unregistered
|
|
it's tie.
1) Java work's anywhere.
2) .Net have very simple native interface.
( visual c++ 2005 is combination of garbage collected code
and native code, it's cool and fast )
|
Previous
Index
Next
Threaded
Edit
Reply
Quote
