Highlights:
If you've written a lot of VFP
code that surely will be your
"funds".
Can you afford throwing that away?
Is there really a need to work with
another programming language?
and do your customers care if
your software is written with X
or Y?
---
Listen, don't start wiggin' out now. The VFP community cannot be canned and
tossed out - keep writting until the OS can't support it I say.
I currently don't see a reason to bail out of VFP and start from scratch
with a new language. And finally, because MS says they are not releasing a
new VFP doesn't mean it will die. You never know what will happen.
---
MS Stopped development on VFP cause IT IS CODE COMPLETE-
i.e. - ya don't need anything else in it, to use it as a development tool.
---
Even if they ultimately come out with a non-VFP friendly OS, it still may be
possible for someone to write a "compatibility" box that allows the legacy
application to run. That would seem to be an easier task then rewriting VFP
or switching to something else.
No comments:
Post a Comment