Highlights:
This is a nail in the coffin. I don't read "will run on 64-bit Windows in
32-bit compatibility mode" as a statement of improving VFP. I see it as a
VFP-friendlier phrasing of what is more likely the case--that Longhorn was
planned so that you won't have to scrap your legacy systems, yet. I recall
getting beat up when Win95 had rolled out and we were still developing our
product in 16-bit FoxWin. It's just one more shortcoming for a competitor
to point out. A statement like that would make me VERY jittery about
starting any new development on a product that has stated no plan to make
use of the future of Windows architecture.
VFP is too good of a language to "deserve" this, but I don't have any reason
to believe that MS has any intention other than letting VFP slip into COBOL
status. :-(
---
Although they say there are no plans to merge, a de facto merge could be
coming, if only because dotnet copies Fox's features.
---
For those who find the work, it will
probably become more and more lucrative. And for that same reason, someone
will very likely continue to build add-ons or other ways to work with it.
But over time, very few new endeavors are likely to be undertaken by
companies that do not already have other VFP ties. And for those that do
decide to replace their legacy apps, VFP looks less likely to be the
language of choice. And, while I'm sure MS didn't build COM Interop into
.NET specifically to crush VFP, it provides at least some easing of such a
path, should a company decide to replace existing systems.
No comments:
Post a Comment