Slashdot Mirror

← Back to Stories (view on slashdot.org)

Advantages Of .NET Over Java

Posted by timothy on from the easier-to-spell dept.

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."

3 of 125 comments (clear)

  1. Re:.NET over Java? You have to be kidding me. by zulux · · Score: 4, Informative


    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 .NET - it will not have Microsoft's .NET libraries.

    99.99% of all .NET applications won't run on Mono.

    Some C# programs can run on .NET and Mono - but not any appplication that uses the Microsoft .NET libraries (99.99% of them)

    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 .NET - not even Microsoft is releasing the next version of MS Office on .NET.

    --

    Moneyed corporations, non-working 'poor' and criminal prisoners are turning productive citizens into tax-slaves.

  2. The main reason people don't like .NET by Joe+the+Lesser · · Score: 3, Informative

    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)
  3. Re:Lets break this down... by MobyDisk · · Score: 3, Informative

    I don't think you read the article.

    #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 .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.

    #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 .NET.