Var just makes it harder to read C# code. For example, the difference between...<p>int foo = object.GetSomething() vs
var foo = object.GetSomething()<p>The int makes it easy for you to instantly identify that foo is an integer. In the var example, what the fuck is foo? A string? A class? An integer? To find out, you must rely on Visual Studio's Intellisense and hover your mouse over foo for a few secons, before Visual Studio will tell you what type foo is. This slows your code reading considerably. And if you don't have Visual Studio, then you have to go waste time reading the documentation to figure out what type foo is.<p>Sure, it save your typing time, but, it waste other developer's reading time.
I'm trying my hand at getting back into some C# coding and found that apparently the language now has var. My first thought was why would a professional, statically typed language have var. Checking out the page I linked to in the submission, you can also do this cool if not slightly funky looking thing where it looks like an SQL predicate just reading from an ordinary array.