Hi, Alex.

>See http://msdn.microsoft.com/netframework/future/linq/default.aspx?pull=/library/en-us/dndotnet/html/linqprojectovw.asp
>
>Interesting article.
>
>Reading the description of the LINQ project shows that great stuff is being added to .NET, but IMHO LINQ should use standard SQL syntax to provide developers with a single learning curve. Beggars can't be choosers, but I hope VB.NET uses a more standards based approach.
>
>The article unnecesarily complicates a very intuitive thing. Why use buzzwords like lambda expressions and expression trees? Keep it simple.

Don't worry so much about this stuff yet. This is still in an early stage. Also, the papers are explaining all the theory behind this. I've been working with F#, C omega and a few of the pure-research languages previous to LINQ, and they are even worst. But the important thing here is not syntax (yet) but semantics.

Anyway, there are ways to make all this simpler. C# and VB are getting better and better support for all this stuff. Remember, all this is at least 18~24 months far from release.

See you,