Slashdot Mirror
Advantages Of .NET Over Java
ansonyumo writes "ZDNet is carrying an article written by one John Carroll that outlines specific advantages of .NET over Java. It's written from the point of view of a Java advocate who has 'seen the light.' First of all, comparing .NET and Java isn't very fair; you have to compare .NET and J2EE. When you level the playing field, most of his arguments readily fall apart."
For more info, check this Register article:2 7833.html
.NET implementations of a Pet Store web store.
http://www.theregister.co.uk/content/4/
Its got some good benchmarks of real-world, optimized J2EE vs.
Very informative (though obviously, benchmarks should be taken with a grain of salt).
Mono [go-mono.org] is a clean-room implementation that runs natively on x86 Linux and interpreted on PPC, S390 and StrongARM.
Mono is not
99.99% of all
Some C# programs can run on
Microsoft released [microsoft.com] the source to an implementation that compiles and runs on Windows, FreeBSD and MacOS 10.2.
As per Microsoft license for this release, you can't do any comercial work with it. You can't modify it and distribute for comercial use.
It's useless.
Microsoft has horrible support for it's languages - they left their Pascal, Fortran, VB users without any support. FoxPRO will probably be next.
I woulden't bet my future on
Moneyed corporations, non-working 'poor' and criminal prisoners are turning productive citizens into tax-slaves.
It's owned/created by Microsoft.
It's new and costs money/time/pain to switch, for hard to see benefits.
(Justified in my opinion.)
"I only speak the truth"
Karma: null(Mostly affected by an unassigned variable)
I don't think you read the article.
.NET. To briefly reiterate, he listed meta-information about methods which is necessary to make it truly useful. Knowing a method name and parameters isn't the whole deal.
.NET.
#1: You referred to property get/sets, but that isn't what the author was talking about. He was talking about external configuration files, environment configuration files, an serialization.
#2: The author explicitly lists what information, beyond the methods, you can get from
#3: You ask "how is this better?" which is exactly what page 3 of the article describers. The author explicitly lists advantages of archives over JAR files. He points out that it isn't a magnanimous difference, but he certainly answers your question.
#4: You've obviously never done cross-language RMI. One of the running Jokes about Java is that Java is great at communicating with other languages: so long as the other langauge is Java. Microsoft has taken cross-language support to a new level - which is one of the things that really attracts VB, Java, and C++ developers to
You've obviously never done cross-language RMI. One of the running Jokes about Java is that Java is great at communicating with other languages: so long as the other langauge is Java.
A running joke that I've not encountered in six years of professional Java programming. CORBA make cross platform, language independent programming a breeze. My current employers hand crafted database (written in C and running on various Unix flavours), communicates very elegantly with a Java frontend via CORBA. For embedded systems too small to run Java, it's the same IDL files but a C based frontend using curses.
Microsoft has taken cross-language support to a new level ...
Really? Could my company do what I described above with .NET? Of course not, as we wouldn't be able to interface with our database. Our one attempt to get it running on Redmonds poor excuse for a server OS made us realise that we'd need considerably more powerful hardware, and more redundancy to cope with Windows little "foibles". So .NET's cross-language, but only if want to put up with Windows.
Chris
So, according to this guy, the advantages are: 1. XML property files
Guess the guy doesn't know about java.util.prefs.Preferences.
"First you gotta do the truffle shuffle."
Even if you used Delphi you would be better off than VB...not an OSS thing but a general usability and code speed, reliability, quality dev environment thing.
Not all decisions are made on which technology is better. There are other factors such as the availability of programmers, third party tools, and technical support. VB beats Delphi hands-down in all three cases. Usability, speed, and reliability are more than adequate with VB to make them non-issues for us.
SQL Server is a load of crap as well.
As far as SQL Server goes, we rely heavily on stored procedures so the availability of freebies is moot for the time being. We also use an accounting package and an HR package that need either SQL Server or Oracle to run, so even if we moved our internal applications to another platform we'd still need to support SQL Server. We used to use Sybase, but switched to MS after v7.0 came out. It was a relatively easy migration, and we were able to reduce our support and maintenance costs significantly.
Incidentally, did you apply the Slammer patch?
I applied the Slammer patch to our SQL servers over the weekend before the worm hit the 'net in full force. I missed one installation of MSDE which did end up getting infected and causing some slowness on our network. I can't say the same for our parent company, however. Their network was effectively down for almost 24 hours while they cleaned up. I ended up putting a firewall between us and the parent company as a result...