3 ms·

HAHA, C# copied Java in many ways, now Java is following suit. Good for them.

• jpitz 13y ago
  What, it copied a single-class, multiple-interface statically typed OO language? Since the lead architect on C# designed one of those that predated Java, I think it is pretty clear what he was copying. http://en.wikipedia.org/wiki/Object_Pascal http://en.wikipedia.org/wiki/Object_Pascal
  • eropple 13y ago
    I think this is a little bit handwavey regarding the historical background. My understanding is that NGWS, and then .NET 1.0, grew out of J++ and the Microsoft JVM extensions being a problem. Most of C#'s semantics, especially with regards to C# 1.0, very closely parallel Java's (right down to stuff like missing generics in the first release), as does large parts of the .NET class library. I don't think it's unfair to characterize it as C# taking a lot of notes from Java, nor do I think it's unfair to characterize Java doing the same thing here. This isn't to say Anders and company didn't significantly improve it, to be clear, but I tend to think they were looking much more at Java than at Object Pascal.
    • jpitz 13y ago
      I don't think it's unfair to say C# took some cues from Java either, but Property syntax, for example, (sadly) has no counterpart in Java, only Object Pascal/Delphi. Historically, the impetus behind C#'s birth _absolutely_ was Java and the J++ debacle. tl;dr - I think we mostly agree.
• pavanred 13y ago
  Looking forward to this. I used to write C# code for quite some time before I started working with Java. And, I must say after using Linq extensively, it almost felt like a handicap to work without Lambda expressions in Java.
• AndrewDucker 13y ago
  Not just copying - I'd love to be able to put static methods on interfaces in C#.