Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

13
  • 5
    Java was a mistake. If you want raw performance (and you often do) then you want to write in C/C++. If you want developer productivity then you want a higher level language like Python or PHP or Ruby or JS. Java (and C#) are middle-ground systems that give you neither the best performance or the best productivity. As it is, C++ isn't so bad - you can get good productivity from it once you know what you're doing. Commented Nov 2, 2012 at 13:20
  • 8
    @gbjbaanb I have mixed feelings about your comment: a few years ago, putting Java and C# on the same level of abstraction would have made sense, but the introduction of LINQ, lambda expressions and async programming features in the newer versions of .NET have moved C# to a higher level (Java is going to catch up on the lack of functional programming in JDK8, but that's still in early access stage). Commented Nov 2, 2012 at 15:21
  • 2
    @gbjbaanb fortunately, WCF is only a tiny part of .NET, and generalizing that to apply to the C# language is invalid. Have you actually used the new features since .NET 3? Because VS isn't such a great development environment at all (in fact, it's truly annoying without ReSharper). So, considering that this very site (and the whole SE network) is built with C#, your comment seems a little inaccurate. Commented Nov 3, 2012 at 0:40
  • 1
    @rotman Please do not reply to other people's answers in your own answer. Answers should only address the original question :) Commented Nov 25, 2012 at 0:12
  • 6
    @gbjbaanb: I would say that it was assertion without evidence that middle-ground systems that give you neither the best performance or the best productivity are a mistake. Given that performance and productivity are both important, the best solution is one that balances the two, and a middle-ground choice like Java or C# is an excellent choice for many use cases. Commented Jan 8, 2013 at 0:42