>I guess the thing about this thread that has been bugging me is there are only two views; those that favor VFP and those that don't. In the past thirty year of development, I have used several development languages. Many of those are dead. Many have evolved into something actually useful. As mentioned, Fox had it days, but now it is viewed as a obsolete language (Like Pascal, Cobalt, ADA, Smalltalk, just to mention a few out of many.) As developers', we should stop staring at our feet and look at the road in front of us. We (VFP) are not at the end of our path, just at a cross road. The question is, which path should we take? Do we keep moving, or stand and die with VFP.
>
>To All: Pull out head out of ground and find a new world where you are marketable!


Foxrpo is not dead. It's just dying. It will die, like all those you mentioned (Pascal, Cobalt, ADA, Smalltalk...), but it will take a few more years to fully play out.

So right now VFP is in phase 7 of a language life cycle...

Phase 1: New language comes out. It is the new kid on the block, lots of buzz
Phase 2: New language becomes King of the hill
Phase 3: Attention turns to noise made by other new languages/platforms coming out which are begining their Phase 1 of life.
Phase 4: What was new language becomes old language and old language begins to die.
Phase 5: Old langauge users start life support, complaining, resistance to change
Phase 6: Old language climbs into death bed
Phase 7: Old language users pretend old language is not dying
Phase 8: Old language dies
Phase 9: Old language users pretend old language did not die
Phase 10: Old language users die
Phase 11: Old language really is dead