Slashdot Mirror

← Back to Stories (view on slashdot.org)

Does C# Measure Up?

Posted by Cliff on from the bring-out-the-byte-meter dept.

An anonymous reader queries: "Windows::Developer is offering a detailed, quantitative examination [free login required] of C#'s performance versus Java, C, C++ and D. 'Overall the results were surprising, although perhaps unexciting, in showing that C# (and to a less extent Java) is, to a good degree, on a par in efficiency terms with its older and (presumed to be) more efficient counterparts C and C++ at least as far as the basic language features compared in this analysis are concerned,' writes the author, Matthew Wilson. I'm only an amateur coder, and confess to not understanding most of the two-part article. I'd love to hear how true programmers view his results, which are too wide-ranging to summarize easily here. How about it Slashdot, as this special edition asks, 'Can C# keep up with compiled languages like C, C++, and D or byte-code based Java?'"

While we're on the topic of C#, rnd() queries: "It's been a while now, since Mono and DotGnu have begun eroding the market power of Microsoft by creating open source implementations of C# and the Common Language Runtime. Over the weekend I loaded Mono and did some informal benchmarking of object creation, intensive message passing, massive iteration, etc., and the results show that Mono is about 90% as fast as Microsoft's implementation after a very short time. I now want to switch my .NET development over to Linux/Mono exclusively, but I want to first settle on a free alternative to Visual Studio .NET 2003. Any suggestions?"

1 of 677 comments (clear)

  1. They can't be using this at Microsoft! by mdonalds · · Score: 0, Troll
    Here are my observations after an hour:

    - The Visual Studio IDE isn't as good as eclipse. In fact when I think about it, it sucks.

    - The IDE's refractoring is no existant. This is fine if you're copying existing design/code or working on something Mickey Mouse.

    - Define an ArrayList add two items. Now how many items do you think will be in the set. 2? Nope, some other amount. And therefore you constantly need to TrimToSize to the empty items. This sucks big time.

    - Threads. Better than Java is some fringe areas, but far worse in key areas. Like how threads aren't reuseable. This leads to more code. Sucks again.

    - foreach is ok. But big deal!

    In summary, C# is just like Java, renamed and changed slightly, slightly better in minor ways, and really overworked and dud in key areas. I perfer languages/libraries that are clean, simple and logical. C#'s aren't.

    There's no way Microsoft developers use this or SourceSafe!