I was pretty pumped when we introduced Generics with the new version of the .NET Framework (http://msdn2.microsoft.com/en-us/library/ms172192). But, I have to say that I am more excited about what we are doing with LINQ. This new initative solves a problem I have encountered on a lot of projects: Why should I use one method to address and access XML data and then a completely different one for SQL data? The manner of querying data for each type could not be more different. Why should I have to remember nuances of these techniques depending on which language I use? What about data sources that do not fit into these two categories? What about a data source no one has thought of yet?

What would happen if we had a way that was common to all sources? In other words, we could have a querying facility built right into the .NET Framework and any .NET compliant language can get in on the act. It is a standard source-agnostic query language built right into the Framework, and there is syntax checking at compile time. Let that last sentence really sink in. There are other things we have grown accustomed to at design-time like Intellisense that are in play with LINQ. Put simply: this is all about making developers' lives easier. A lot easier.

Here are pointers to some resources:

Now is a good time to get on board. BTW: this mug at CafePress is pretty cool:

http://www.cafepress.com/dotnetinfo.20494355

 

 

     Rock Thought for the Day: Remember the Clash's great song, "White Riot"? Great punk of the time. When the Clash hit the US, for me it was about the music. The UK was having riots between kids because they were wearing the wrong clothes (punk has a dresscode, don't let anyone fool you). For me, it was always about the music. The punk music I heard recaptured the spontaneous freedom and energy that rock and roll had always shouted through the PA system. I hear it now just as well as I did then.

    Rock On