This morning I saw that industry leaders (including Gartner which agreed with you about VFP even before you did, as well as IBM and other heavy hitters) are saying that the days of "the programmer" are over; armies of developers will be replaced by handfuls of analysts creating scopes for auto code generators. IOW the next generation of "visicalc" is upon us.

If this is true then people might be best advised to STAY PRODUCTIVE any-which-way while beefing up on design methodologies and other skills that will help them become one of the analyst technocrats when the time comes. The VFP community already has an advantage because so many of us are accustomed to working alone or in small groups doing lots of design work ourselves. For people who are already well along the path to an analyst role, "C# vs VFP" could be a monumental distraction at a time when our decisions can make a difference to our standards of living for the rest of our lives.

I just don't think that "the right thing to do" is a one-size-fits-all garment, or that we aren't missing the wood for the trees in some of the discussions.