>>>As bad a perception that it makes, VFP is at it's heart, an xBase product. Without the xbaseness in it, you would not have all the local DBF handling.
>>>
>>
>>Not to mention continuing to support bad habits gained from long use of xBASE products. VFP could do with a little less 'backwards compatibility' in favor of a cleaner design and less baggagen from the distant past...
>>
>What bad habits? Using xBase code when a SQL solution is available? I always use SQL anyway, but The Hacker's Guide and Ed Pikman say that sometimes xBase is faster, or perhaps a combination.

Not as portable, and it doesn't make people change their mindset to an OOP environment - I've seen too much procedural code ported to VFP (I've even been responsible for doing some of it) where rethinking the design to take advantage of the OOP environment woudl result in a better app.