>... and there's too much of it. Intellisense will get you the next name in the sausage, but you still need to know where the sausage needs to start. And you may be using a piece of abandonware at that.
>
>Define "too much."

Takes more than five minutes to find the class you want to use. You pretty much have to have some map of the inventory in your head before you start looking for anything, and then when you think you've found it, it turns out it's not intended for how you mean to use it, you have to search for a more suitable one.

>The .NET framework is unquestionably complex but I don't think it is bigger or more complex than it needs to be. Anyone who is going to use it day in and day out should be willing to learn at least the most important parts. The rest can be learned as needed.

That's the kicker, I couldn't even find which parts were important. They all seem to be, if you read their descriptions.

> You wouldn't expect or want a streamlined way to fly a jet, would you?

That's the kicker #2, and thanks for proving my point: why would I want to fly a jet? Even a simple car is hard to park in some places, and a jet only takes you to another jet-capable airport, not where you want to go.

>My hat is off to you for all the different languages you have used. I have worked with only half a dozen or so languages, all mainstream.

Being a partner in two startups here (before my US stint) I had to be the jack of all trades, just like most of the rest of us. So yes, had to do a lot of weird stuff along the way. Ah, forgot my worst offender: the command set for Olivetti document printer. That was enough to wither all the plants in your house just to find the next code you need to use, so much negative energy emanating from it :).