Me too. I still think it could be used to create some effective stand alone apps that might sell for fifty bucks or so.


>I hope that we still have some years to go before that happens.
>
>>I'm retired. I program VFP just for me :) It's a treat and I'll continue to use it. My only fear is that sites such as the UT will drop VFP support and I'll lose all those wonderful code snippets and solutions that are here.
>>
>>>Here's how I see this.
>>>
>>>For contractors offering their services to consulting firms VFP is probably dead.
>>>For developers that want to work for big enterprises VFP is probably dead.
>>>For businesses offering solutions to vertical markets. VFP is still a viable development environment.
>>>
>>>I think the key here is : If your work means that at the end of the day your client is the owner of the source code than VFP is not going to be the development environment.
>>>
>>>
>>>>Hey Denis,
>>>>
>>>>I can't agree in general. If a developer wants to stick with VFP and take the chance that they will always have work until the end of their career you make a point.
>>>>
>>>>.Net *is* evolving, but those evolutions build on previous versions and it gets harder and harder to jump in from scratch. I've been doing nothing but .Net for almost 2 years as a developer and to do anything as deep as what we do in our VFP apps is challenging. And it gets more so as MS steers the framework more towards technology platforms like cloud computing which is far outside what the VFP community has experience in.
>>>>
>>>>But I suppose it comes down to what you want to do with yourself, If you want to stay in your niche and are reasonably sure you can stick with VFP as long as you want, well God bless you. I'm just not that type of guy - I believe I have to maintain and continually master a skillset that is currently en vogue or not be hireable.
>>>>
>>>>Potential employers demand current skills - sometimes unreasonably. It was a strong reality check for me to be turned down for work because I couldn't explain some nuance of the WCF even though I was, arguably, one of the best VFP coders on the planet 10 years ago.
>>>>
>>>>I get emails every week from former VFP all-stars who are dying on the vine and cornered. I don't like it one bit. I try to help but if they've ignored trends and not made themselves adaptable, what can I do?
>>>>
>>>>>
>>>>>>Regarding the VFP faithful and experienced, just my opinion, it's time to move on - err...way past time. .Net is evolving rapidly and very hard to master if you haven't already caught that train.
>>>>>
>>>>>For those lucky enough to still make a living with the Fox I'd say the longer the better. In the meantime .Net is evolving and all the tools that comes with it are getting better and better. So I see this as a win-win situation. When really really forced to leave VFP .net will be even better than what it is now. If a developer can afford to pick VFP as a development environment and stick with it then who the heck can say he shouldn't because the Fox is dead? The rest is crap. Fox is not dead. Cobol is not dead. Fortran is not dead. and the list goes on and on. If the tool suits the needs than so be it. To me it looks like a bunch of frustrated developers. VFP bashing because many liked it a lot but were forced to move to something else.
>>>>>
>>>>>Long live the FOX 8-)