What's the next big thing after LINQ? [closed]

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance. Closed 12 years ago.

I s开发者_StackOverflow中文版tarted using LINQ (Language Integrated Query) when it was still in beta, more specifically Microsoft .NET LINQ Preview (May 2006). Almost 4 years have passed and here we are using LINQ in a lot of projects for the most diverse tasks.

I even wrote my final college project based on LINQ. You see how I like it.

LINQ and more recently PLINQ (Parallel LINQ) give our jobs a great boost when it comes to more programming power and less lines of code leading us to more expressive and readable code.

I keep thinking what could be the next big language improvement for C# after LINQ.

I know there are some promissing language features coming as Code Contracts, etc, but nothing having the impact that LINQ had.

What do you think could be the next big thing?

---

Reactive Extensions

The Reactive Extensions (Rx) is a library for composing asynchronous and event-based programs using observable sequences and LINQ-style query operators. Using Rx, developers represent asynchronous data streams with Observables, query asynchronous data streams using LINQ operators, and parameterize the concurrency in the asynchronous data streams using Schedulers. Simply put, Rx = Observables + LINQ + Schedulers.

---

ParallellFX specifically. Concurrency generally.

---

I would love to see syntactic customization a la Boo's access to the compiler pipeline.