I don't think you understand how awesome namespaces are.

I'm tired of reading the exact same list of commonly used namespaces in each and every file when all I really care about is the one or two namespaces that only this class imports.

It's recommended to put your using declaratives inside of your existing namespace. You can even separate them further and put them within class definitions. So you can organize them to work better for you.

I'm not really sure why you're typing those out though.

I'm tired of reading the exact same list of commonly used namespaces in each and every file when all I really care about is the one or two namespaces that only this class imports.

No comment here. I don't get the reading difficulty; it sounds like you just have an axe to grind.

How many of your source files don't use System and System.Collections.Generic?

Several, actually. Not sure why you'd really need them every single time. But this really doesn't matter; who cares if I need them in every source file or zero?

How many times have you seen a namespace collision that involved a class from System and System.Collections.Generic?

Several times though it seems to happen to me more often in Java. Really though, it all depends on your project.

Essentially, you come into a big system and need to start coding. Someone created a better String class because, in .Net 1.0, something sucked about the built in one. Now you're on .Net 4.0 and String and String have wildly different methods. Without namespaces you'd be screwed.

This happens all the time in incredibly large, complex systems. Sometimes people have a very valid excuse to replace or augment existing classes and sometimes they don't; regardless you need to handle both.

Now you sound like a Java programmer. "Don't worry about all that boilerplate code, the IDE will add it for you."

Do you have something against using tools to...do things?