Here is yet another article (a very well written and informative one, I might add) about MS’s latest announcement: Good News, Bad News for Visual FoxPro Developers by Stuart J. Johnston

Here’s a taste:

What makes VFP unique is that it closely binds a data-centric language with a local database engine, unlike any other developer tool,” says Ken Levy, a former VFP product manager. Because it was not directed towards the same markets as Access and Microsoft Office, the VFP product group was pretty much left to its own devices.

…

Through the years, FoxPro evolved into VFP, becoming another of the company’s “Visual” products, replete with integration into Visual Studio. But it was always somehow out of the mainstream. To some extent, that helped VFP establish a following that verges on cultish.