Just something I had in mind, in addition to what Ali said:



1. In addition to library implementations (like enumeration pipeline, expression tree, etc.) LINQ is built on top of a couple of language features (anonymous types, extension methods, lambda expressions, implicitly typed variables, and query keywords), which provide some compile time benefits. (like type-safety) I think LINQ can’t just be ‘implemented’ as a class library in Java, unless you provide some pre-compilation phase and an IDE to simulate that. Let me know if I’m wrong.

2. LINQ is a very broad set of features targeting different aspects of development. (for example, its LINQ2SQL provides some kind of ORM. We do use LINQ in our project a lot, and it really helps us, but nothing ORM-related.) You should specify what kind of thing you want to do similar to the LINQ way.