>>>
>>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.


>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.

>
But it is a huge revolution. We all know that the vast majority of existing developers are VB6 or prior and thus have no practical experience in OOP. No stepping stones there.
>

For them, it is a huge step. That is why I qualified my statement for those that have embraced objects and OO.

<
Us VFPers have only a marginal advantage over the VB6 folk given the depth of breadth of .NET over VFP's.
<

That depends on whether you couched your knowledge of OOP through a VFP only lens. The same can be said for client/server development. If your only exposure is through views, you are working from an extreme disadvantage.

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...

<
We have one or two stepping stones, early in the voyage, and after that we meet up with the VB.notNET folk.
<

I highly discount and quite frankley, don't take the dot notters seriously.