Pablo...

You don't have to justify your use of VFP to me. As I have said on numerous occasions I THINK VFP is a great is a great tool. At the same time, I am aware of the outside perceptions of VFP. I have the ability to separate the market economics of a tool I use from the personal feelings and love I have for the tool. A great tool void of marketing does not make for a good combination. For a long time, I fought long and hard to get VFP marketed. After a while I recognized reality and moved on to other priorities.

If you love VFP and you can find well-paying VFP work, I say go for it and use VFP. At the same time, have a plan because the fact is, the overall market for VFP is declining. This is not me making it up and it is not me preaching doom and gloom. It is me commenting on the trends I see. You may agree and you may disagree. Most importantly, don't take your specific sitatuation and make a propensity argument that because things are OK for you, they are OK for everyone and VFP in general. I think for every 1 VFP developer who is content, there are 10 who are either in trouble and need to move now or are making plans over the next 12-18 months to move way from VFP to something else.

Ken Matson I think represents the prototypical situation, both in terms of how VFP factors into development. From an upgrade standpoint, I definitely see a trend where less and less folks will upgrade? Why? Because less and less new projects will be written in VFP. If you have existing apps working in a version that you are not likely to take beyond the version it is written in, there is no reason to upgrade. This will result in a vicious cycle.


In any case, be comfortable with the tool you use and separate your personal feelings for a tool from the market realities of that tool.