>>>> It's just that your sigh of relief that the era of rapid change
>>>> is over is a bit premature. <g> My bet is that change will be rapid and
>>>> accelerating.
>>
>>I disagree, in the sense that the objects surfaced by the .NET framework have the opportunity to shelter programmers from this rapid change in hardware of which (I assume) you speak.
>
>The rapid change is not hardware, it is... everything.
>
>We have gone from Dos to Windows to Client-Server to Internet to .NET to ??
>
>My guess is that it is not in MS best interest to shelter us from the rapid change. Ever since Dos, MS seems to have a gift for profiting from change in the PC environment. Why would they want to slow down the rate of change?

I have to agree with you, Mike.
C# will have "professional respect" for only as long as MS wants it to. [and I do wonder if the C and C++ folks accord that "respect" to C#. And I'm also of the opinion that MS may never have intended to afford VF/VFP that 'respect' in the first place]

I may get into .NET stuff some time in the future... once the product has passed puberty.
I also think that anyone getting into a new language/platform/whatever ought to do so enthusiastically when they do. Mr. Blankenship is doing so, and I say good for him.

Right now MS has the development community basically convinced that .NET **IS** a success. It remains to be seen if companies adopt it to the degree that MS anticipates/needs. My guess is that MS will use any means to (effectively) force the issue and that they will succeed. But that may take quite a while yet.

cheers

>
>Best,
>Mike