Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
What is the VFP community missing?
Message
General information
Forum:
Visual FoxPro
Category:
Other
Miscellaneous
Thread ID:
00437641
Message ID:
00438390
Views:
15
People have been saying that VFP has been dying since it was released. You can create your own reality on your views of the facts. My view is many companies and government agencies are going to keep using VFP for the next five years or until it is not cost efficient to do so. Then they will find another tool to get the job done.

As a developer, I agree with you that we need to constantly look at the options. Microsoft is still upgrading VFP with VFP7 being released next year and VFP8 on the drawing board. Yes, MSFT wants SQL Server everywhere and are spending tons of money on .NET. I have been saying that the Internet and SQL Server are bigger in demand than VFP. Does that mean I can’t find a VFP job and make a very good salary? No. I just changed jobs in May and had three jobs to pick from and I choose the closest one.

I don't agree that VFP's lot in life has been determined except in your mind. I think with the .NET and next version of VFP will be an interesting time as how MSFT can pull it all together. I think VFP will be in a good position. At least better than it is now.


>Hi Perry..
>
>This has always been my point. I see a lot of "good" intentions here. I remember the the VFPDA initiative from last year. Nice idea. However, what does it really mean? The concept of community, getting the warm-fuzzies, etc, it is all nice. In the end, what does it really mean? I guess it depends on how you couch the question.
>
>What if you are somebody who is faced with very few options? What are those contacts in the VFP community going to do for you? Not much. I know this is not a popular view point - but it does reflect reality.
>
>The fact of the matter - nobody here can control the destiny of VFP. It is too far gone. MS has a plan. The plan however, may or many not be in your best interest. If you plan is to stay in VFP for the next 5 years, the MS's plan is not in your best interest. If on the other hand, you plan on transitioning, MS's plan is good. Keep in mind here that I have not stated whether I agree or disagree with the "plan". That is irrelevant.
>
>The study of law has been of immense value when it comes to analysis. A good example deals with negligence and assigning liability. The negligence formula, at first glance - is very simple:
>
>1. You have a duty of reasonable care under the circumstances
>2. That duty was breached
>3. There was causation between the breach of the duty of reasonable care and
>4. The Injury that resulted...
>
>You need all 4. If one is missing, no liability. Even if you have the first two, while you still have negligence, it is only negligence in the air. If there is no direct or legal causation - or no injury - no liability...
>
>
>If I am faced with a fact-pattern and am asked if negligence exists, I first analyze to see if some duty existed. If I can find no duty, I don't care about elements 2, 3, or 4.
>
>Turning back to the VFP world, I look at many factors. The first is the overall market for either the developer tool I use or the one that I might adopt. If the market is thriving and growing, I will continue the analysis of whether I will adopt the tool. If the market is in a decline, I stop analyzing. Why bother? Anything more, and you are wasting your time. You have your answer. It is time to move on.
>
>Ask yourself if you would adopt Delphi. ManyP'ers will tell you they would not. On one hand, they may tell you that from a tool standpoint - it is very good. However, they may also tell you that Borland/Inprise has had problems. And, if you look in the paper, it is not as though Delphi jobs are jumping off the page.
>
>An interesting question, and one that will never get answered honestly would be which VFP developers today would adopt VFP as their primary tool if it was first presented to them today. Remember the analysis that gets applied to Delphi. Why would VFP be any different. The reason most people use VFP is because they use VFP. It is what they know. It is a terrible circle to be in. For a while, things will be OK. However, it is the time when things are OK that one needs to plan for the future - and not get stung.
>
>The harsh reality is despite the best wishes, hopes, and prayers that people have, VFP's lot in life has been determined. Stick a fork in it - it is not only done, it is well done. Use it up for all that it is worth today. Get the most you can get out of it - while you can. Don't be dillustional that today's billings translate into future success of the product.
>
>The day is going to come. The questions is - will you be ready for it??
>
>My bitter - yet reality based 2 cents...
>
>< JVP >
DLC
"Use the Right Tool for the Job!"
davidandcynthia@email.com
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform