Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
What happened to the Powered by Visual Foxpro logo?
Message
De
30/07/2002 14:25:59
 
Information générale
Forum:
Visual FoxPro
Catégorie:
Autre
Divers
Thread ID:
00683777
Message ID:
00684086
Vues:
37
>The purpose you assert is to raise the profile of VFP in a cost effective way. Cost effective yes, but will it raise the profile? No, it won't.

That is entirely your opinion, yet you state it as fact?

>If MS is not willing to promote the tool, why should I expend the time and effort to do so when in the end, it won't make a bit of difference.

Well, as you've stated in the past, the VFP market is a mature one. Its not going to bring MS any great revenue and they are actively pushing .Net. Fine, but, they are still improving VFP for its developer base and given that we are well aware that VFP is not an MS "cash-cow", then why can't enthusiastic VFP developers do their own little bit to help raise the profile of the tool of their choice? VB developers didn't appear to get excited by their tool. VFP developers are generally excited by their tool. The difference IMHO is mostly the community - isn't this the very thing MS are trying to encourage right now - the evangelism of .Net products/languages and the development of communities behind them? I suggest that a very strong lead was taken from the Foxpro community by MS who have observed in amazement since the outset, the enthusiasm of this community. I don't see how you can fail to understand this point or reject it? For my money, I don't care if MS fail to market VFP - my only concern is that they keep improving it.

>In the end, did it make a difference? I contend it did not and will not...

Then this the same for VB apps too. Irrespective of how people perceived VB, "did it make a difference" ? No, it didn't because MS just provided VB.Net - a language that is probably as accesible to VFP developers with their OOP background as it is to VB developers who have a little more familiarity with the syntax - beyond that, it is a quite different language to classic VB, and now, the job is learning the framework. For VFP developers, learning frameworks is almost second-nature given the number of VFP frameworks that exist in support of this product. I think you argument just fell over on this one.

Best
-=Gary
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform