Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
New case study in MSDN Flash
Message
De
09/12/2003 08:21:52
 
Information générale
Forum:
Visual FoxPro
Catégorie:
Autre
Divers
Thread ID:
00856811
Message ID:
00857138
Vues:
28
>Hold on...where do I say - either explicitly or impliedly that it could not have been a success story if they stuck with Visual FoxPro when migrating to the web? Likely, we would not have heard about it because MS would have never commissioned a case study.

So, what you meant by "if it is a bona-fide success story - that is all that counts"? Taking off any of your usual lawful rhetoric, your statement may lead to this perception, at least it did to me. So what really counts? Your words, your (hidden) intent or the perception they caused?

>I find it interesting that with some in the Visual FoxPro community - .NET gets panned because it is new, untested, immature, etc. etc. Now - some 2+ years down the road, when apps have been written and deployed - .NET still gets panned.

No, it gets panned because of things like that, "success stories" that are nothing more than cheap marketing at the expenses of long term proofed tools like VFP, that is being deliberatelly stagnated to be further dropped from all current developers toolset.

>Your post confirms to me that with some, Visual FoxPro must be promoted at any and all costs. Why? Because it is the tool that you use - and therefore, it must be promoted at the expense of all others.

My post doesn't confirm anything. When you say that "VFP must be promoted at any and all costs" you should be delirating because VFP ISN'T promoted by any means and at any cost!

>Personally, I don't think the issue is with case study per se - and the fact that .NET was used. I think the problem is that .NET displaced Visual FoxPro. Had the case study discussed displacing VB 6 - I don't think there would be the backlash.

Currently .net didn't displaced anything (".NET displaced Visual FoxPro"), at least in the scale MS thinks it should have (how do I know what MS thinks? I don't, I'm just inferring), instead MS is pushing in all the ways they can, developers to the .net ship. As many already commented here and elsewhere many VFP so-called "gurus" are also leading to that. What cannot be accepted is MS stepping over a (almost) dead body to promote their new beloved baby.
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform