Hmm to say "no", first one should know it thoroughly. If someone knows it thoroughly then likely she/he is already thinking "yes" and using it:)
The bottomline is each and every language/tool might be powerfull depending on how much you know of it and how can you use:)
I'm a solo podiatrist-programmer who has used VFP since its implementation in 1992 or so. Laws change fast and require RAD changes that only VFP9 programming overcomes (for the solo-me, as such). I have no doubt that my VFP9 podiatry-apps are the best out there. Corporates don't specialize in small sector niches.
For small business, physicians, niche-programmers, etc. I'd probably still recommend VFP as the only RAD progamming tool for the next 10 years (the life-expectancy of Vista ). Honestly, I feel sorry for other core programmers and engineers (Net, VB, C, etc.) that have to endure the hype of not making money nor beauty for themselves, just their corporate sponsors.
VFP9 allows my older apps to gradually evolve (as languages enlarge) without mutating (A.K.A. mutilating) tricky code. Unlike bio-evo-science (which erroneously assumes extinction-prone raw-mutations!) ... VFP9's *gene-pool* has truly macro-evolved: via smart X-base designers, Microsoft gurus, and these blessed-MVPs (check out their awesome webs). Such robustness may be destined to out-survive (again) vs. the novice 64-bit core languages out there (I may be wrong).
Kludginess and bugs (mine) do require much patience to overcome. I still labor hours on tweaking report listener objects, calendars, and such, that MVPs and others have graciously posted on their webs.
Cetin, I have extreme respect for your words and humbly stand corrected in anything you say. For me to pity one evolved-language over another may seem a bit bigotted, as each language indeed has its benefits.
My corporate friends are suffering under VB and C++/Sharp for Intergraph here in Huntsville, AL. They engineer very well with these languages. But they might architect better in VFP9, especially if their personalities are prone to hyper-creativity.
Their corporate products may be less kludgy than VFP9's graphic handling, and I'd venture to guess .NET is pure beauty for Vista-GUI and 64-bit handling. I'm scared to delve into .NET for at least a few months (unless you strongly suggest I learn .NET for really beautifying or accelerating EMR medical apps).
Thank you very much, Cetin. I glanced at IdeaBlade's Devforce websight (by your recommendation) but am a bit sceeer'd to toy with it for now ... that website looked so corporate and towering for an underling like myself.
My latest VFP9 apps are so creative, complexly evolved, powerful, etc., that I fear (with my limited IQ) being able to transcribe well into RAD .NET Devforce, especially as a puny developer. I've outdone myVFPapps with many mind-boggling VFP excellencies and plenty of WIN32 API stuff that you MVPs and others have so fruitfully modeled:
* Your Win32 "getcarot" routine coupled with Mike Lewis's auto-phrase logic and Alex's list-object query-logic have made intellisensing med-phrases in editboxes an extreme asset for physician-charting of complex diagnoses, medicines, procedures, and EMRs. I'm so productive with this!
* Marsha, Andy, Tamar (and the VFP community) have demonstrated extensive COM use with MS Office that I've already fully integrated in my apps ... and hundreds of other venerable technical creations, and scholarly tricks of the mind that inspire enough.
* Carlos' statusbars seem coolest (for now) ... though I've not seen how they behave with aero-themes.
* Doug Hennig's report-listener logic, Win32, and a few Javascripts enabled me to create cool Window's Desktop-Calendars (HTA/HTML format) that hyperlink VFP-records even under IE7's LAN scrutiny.
Etc. ... Yet I hope to look into Devforce's trial version this summer or sooner, when feasible.