Slashdot Mirror

← Back to Stories (view on slashdot.org)

C# From a Java Developer's Perspective

Posted by timothy on from the curve-before-a-meeting-of-lines dept.

Microsoft's C# has raised eyebrows, interest and debate since its official announcement last year. The prolific Carnage4Life (Dare Obasanjo) has completed a detailed comparison of C# and Java, outlining the things that are identical, similar, nearly the same, or completely different between the two languages. If you're considering learning or applying either one, you might benefit by reading this paper first. There are some other excellent comparisons to be found linked from the Open Directory Project as well. Update: 11/20 03:35 GMT by T : Note: here's a mirror; interested readers who mirror the mirror get good seats in heaven.

2 of 507 comments (clear)

  1. Why do I get the sinking feeling by GISboy · · Score: 4, Funny

    with C# that "cross platform" will eventually mean Win9X, ME, NT, 2K and XP?

    Or in some ominous "Morpheous" like voice:
    "The .NET-rix is everywhere...."

    Or maybe I'm just reading too much into it... after all, Microsoft is doing it for the good of the community and Developers (developers, developers, dev....).

    BWAAAAHAHAHAHAHA...I actually kept a straight face while typing that...heh.

    {sniff, wipes tear from eyes..heeeheee}

    --
    If it is not on fire, it is a software problem.
  2. Re:The lesser of two evils by redcup · · Score: 4, Funny

    Java and C# are both "closed" languages controlled by large corporate entities with their own self-interests in mind

    Agreed - but Java at least attempts "write once, run anywhere," (with debatable success) whereas M$ C# attempts "write once, run on Windows XP, with Windows Messenger and a .Net Passport or else"

    I have a lot more faith trusting my applications and business to a company that isn't trying to take over every purchasing decision we make. If you have read the fine print that comes with Windows messenger - the other half of .Net - it essentially gives Microsoft the right to modify the application at any time, with out notifying you. Oh, and these upgrades might not be free! The bottom line? Microsoft is going to decide sometime in the future to cut you off, and then make you pay. And you would trust these people not to do the same with C#??

    One day your app or service isn't going to run, and all you see in your logs will be "Call Miscrosoft to obtain a license to run C#"

    --

    RC