>>>>Mike has actually been working in .NET for a number of years and is doing so very successfully. As I understand it from your contributions, your knowledge of .NET is limited to reading what other people frustrated about MS decisions have told you about it and you have never written anything with .NET which was then "broken" or for that matter have never written anything with .NET at all.
>>>>
>>>>The idea that somehow this makes Mike the guy with no mind of his own and to label him as a "Microsoft apologist" doesn't give you a lot of credibility.
>>>
>>>Yet another good reason not to get into the dot net boat. One has to waste a year or two of frustration, to master a tool and wait for a chance to ditch some of the work because M$ [strike]forced[/strike] gently offered new [strike]buzzwords[/strike] technologies - all that for the dubious pleasure of being qualified to tell Mike that he's hooked on the thing. As if we didn't know that without the effort.
>>
>>Dragan,
>>I was writing .NET applications and getting paid for it while I was learning. The first app I wrote was for my regular employer and I had a book open next to me the whole time. You don't need to master .NET before you can be productive with it.
>
>Of course. You only need that if you want to say anything suboptimal about it.

I wouldn't say you need to be a master to criticize it. Some real-world experience with it and a little objectiveness, maybe.