3 ms·
It's been a while since I last spent much time with Java, but to my knowledge it's still missing: - User-defined value types - Lambdas - An equivalent to LIN
by bunderbunder 14y ago
It's been a while since I last spent much time with Java, but to my knowledge it's still missing:
- User-defined value types
- Lambdas
- An equivalent to LINQ (and PLINQ)
- Language-level support for asynchronous programming
- True generics (Java's implementation is essentially syntactic sugar on good old-fashioned typecasting.)
- Extension methods
- Late binding
- debacle 14y agoMost of those have nothing to do with threading.
- j_s 14y agoGGP: While I don't disagree that C# is good, I don't see how you could say that Java is in any way behind. GP: [List of features where Java is behind.] (May have missed that the sub-thread is about 'scalable, concurrent systems', though typical C# development leaves threading worries to ASP.NET/SQL libraries.) Personally, I would appreciate it if you'd share how Java threading beats C# threading, particularly C#'s async/await. I don't know much about Java.
- bunderbunder 14y agoFair. I had interpreted you as saying you didn't feel like Java was far behind C# in general. I'm not terribly versed in what Java's got going for it in the concurrency department, so I'm not really qualified to speak to that. The stuff that's been happening in C# and .NET since version 3 is pretty fantastic, IMO, but I don't really know the details about how what Java has compares.
- debacle 14y agoNo, I greatly prefer C# to Java. I just prefer the clarity of thread management in Java - it feels a bit more high level than C#.