Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Should dotNet become VFP?
Message
De
25/06/2004 16:18:55
 
Information générale
Forum:
Visual FoxPro
Catégorie:
Autre
Divers
Thread ID:
00917121
Message ID:
00917378
Vues:
26
Pretty sad when a legit question is greeted this way. Clearly, I hit a nerve - and a grain of truth.

I'd say so (especially the truth part). 4 years ago when you were talking this way, I didn't agree. With each passing year I've seen the providence of your remarks.

Someone made a rather unsophisticated remark that your predictability was 'boring' (or something to that effect). You've been consistent.

The best observation I can make about this apparent 'mental block' regarding tools beyond VFP actually comes from a remark that Walter made. We were talking about Crystal Reports and books on CR, and he made a comment with respect to learning curves, books, and developer creativity (and I certainly didn't disagree with him).

Though it was on a different subject, I think the concept applies here, but in reverse. There is a level of hostility and prejudice against other tools (like .NET). It is partly because some just don't want to apply the same creativity to come up with solutions that was applied when these people were learning about VFP.

I watch all the posts on VFP9 and the beta. Clearly, everybody is stoked. I think, in general, that's a good thing. It would be an even better thing if that same energy were applied to looking at other tools, with an open mind - it might make some realize that VFP isn't the only tool around for doing desktop/client-server apps.

I'll grant this - for years, many I.T. folks dismissed VFP, in part because they had a limited understanding of VFP's feature set. I ran into it many times. However, I think the tables have turned, and some VFP folks hold a similar attitude about tools beyond VFP.

Kevin
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform