>>>>
>>>I don't doubt that there is lots of work on-going with .NET, involving lots of people who are "experts" at some other development environment.
>>><
>>>
>>>If a group of people know more about an environment than anybody else, they are the experts. It is a relative thing.
>>
>>C'mon John. You know that isn't true.
>
>It is absolutely true. A working defition:
>
>ex·pert Pronunciation Key (kspûrt)
>n.
>A person with a high degree of skill in or knowledge of a certain subject.
>
>If a group of people have completed chapter 1 and the rest of the world has not opened the book yet, the folks that have started are de facto experts.

Pure unadulterated CRAP of the highest order! And I know that you know that too. Why would you say such a thing when you yourself know it is patently false.

When Alan Shepard went into space for the first time you believe that made him and the whole U.S. space exploration team "experts" at space travel? They did far more than just read, yet we ALL know, themselves included, that they were no where near "experts" in space travel.


>
>
>>Does it really? Our VFP framework deliverers delivered 'interesting' frameworks using VFP's 3 version. They made MAJOR changes once they had a better understanding of VFP's OOP and how better to exploit it. In some cases maintaining upward compatibility was impossible. Now if this is the case with a OOP of less than 30 classes and only basic capabilites (OOP-wise), what does it say for a widely integrated product (.NET) that has thousands of classes and much more complex OOP capabilities and continues to change on a weekly basis???
>>
>
>I am not going to even try and compare the world of VFP frameworks with .NET. The bottom line is that today, you can deliver apps in .NET and apps have been delivered.

No that is decidedly NOT "the bottom line". At issue is whether .NET applications deliered today (or in the reasonable future) are anywhere near well and properly and efficiently done and run. I say none of them can be. Simply because there is too much yet unfinished and/or clean and/or fully understood for it to be any other way.

>
SNIP
>
>I suspect those that have the ability to pick stuff up quickly will do the same in .NET as those who work hard. Those that have a difficult time or who are just plain lazy will find reasons to knock the product...

Now that is a "shot" but I will ignore it. Even with picking stuff up quickly there is years of learning to be done. KevinM noted that it took him several months just to document the class relationships for himself. As of today he might well have to start over, since things have changed quite a bit since he began that effort.
For the record... I don't think I'm lazy and I am not knocking the "product". I am saying that it is huge and still developing and inadequately documented, severely limiting the audience for it at this time.

>
><
SNIP