It's either that or we might as well be using Phantom...

http://www.apocalypse.org/pub/u/antony/phantom/phantom.htm

Having said that, I found a website sometime ago that laid out the general criteria for a language to be viable for continued use. I don't remember where it is and I searched for it to no avail on google (it must be dead also now), but it went something along the lines of:

Requirements:

It is actively being developed.
It is being taught to new programmers (?).
The owners are still collecting royalties for sales.
It is being used commercially.
There is a job market for programmers who know this language (? diminishing).
Books on this language are still being written.
It has at least one website with recent content provided by users who host conferences and will track down and assault anyone who so much as hints that their cherished language is no longer among the living. (Dead on)

I think VFP fills most of the requirements... :o)


>If VFP will always be a win32 app and Microsoft is moving to a new API, we need to start learning the development tools that will best exploit this new API (ie. Visual Studios .NET)
>
>VFP is a tool, we are developers. VFP and all win32 apps will be supported in Longhorn, but customers may not want any new win32 apps developed, so we need to do the math and move on.
>
>Move on and continue providing solutions for our customers using the best technology available.
>
>I am a veteran VFP devlopers (since 1987), I am willing to expand my horizons.
>
>
>.NET, C# Longhorn ... Bring it on!