Building Tuple

http://msdn.microsoft.com/en-us/magazine/dd942829.aspx

They're proud of it, damn it! It just wouldn't feel right to walk up to him and tell him that this would be trivial if their poor excuse for metaprogramming by way of generics didn't suck balls (``we didn't feel the time we would spend adding eight more tuple types would be worth it'', WTF?!1), and that anyone using tuples are damn well gonna compare them either structurally or not at all. It would be like kicking a puppy.

And what's with the ads? Are MS so poor they have to scrounge for small change in their developer resources now?

At least it's not mutable.

The whole reference/structural equality thing in .NET sucks anyway, this just adds to it.

we were unable to find compelling reasons for Tuple to implement interfaces like IEquatable<T> and IComparable<T>
"Instead of fixing .NET so that implementing interfaces that aren't used doesn't add overhead, we'll just not implement those interfaces." Great.

Also, the code in the article was invisible in Firefucks. MSDN quality.