>>>I thought the issue here was what kind of new music is made, not whether the old music still plays.
>>
>>Depends how you define "no future". If I say my coffee cup has no future, does it vanish immediately, or can I still use it? If I can use it tomorrow, then that's already my coffee cup in a future. So it has one.
>>
>>IOW, "it has no future" is a tricky statement, a sales pitch if you want. A dogmatic, "needs no proof" shoveling statement, designed to put the opponent on the defense. Almost like the classic FUD coming from M$'s PR kitchen. Wait...
>
>I didn't say it has no future (nor trying to put anyone on the defense). That was Bill.

Yes, it was Bill. The "how you define" had a rhetorical "you"... should have been "how one defines".

>I think it has some future in terms of maintenance work on legacy apps. Not so much for new development. It's been a while since I heard of any projects like that.

When building a big project from scratch, I'd scratch my head a lot before deciding on the platform (not just the language). But for any smaller project I'd still stick with VFP simply because of speed and ease of development (and because I'm on the top flat part of the learning curve).

OTOH, there are big VFP projects out there, with ongoing development, like the million webpages with wc.dll that you can just google out, plus the unknown number of desktop apps. That you don't hear of them only means that you don't hear of them.