Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
VFP - .NET blog
Message
Information générale
Forum:
Visual FoxPro
Catégorie:
Autre
Titre:
Divers
Thread ID:
01397536
Message ID:
01400272
Vues:
85
>>What I said was:
>>
>>They change things that break code . . .
>>
>>I've shown that in a previous reply.
>>
>>They go off in different directions . . .
>>
>>Development techniques and recommendations have come and gone in .NET
>>
>>They put forth new data acess techniques . . .
>>
>>You did not dispute that.
>>
>>And eventually they will get rid of .NET completely and we'll have to rewrite everything again . . .
>>
>>Purely an opinion, but not one that is indefensible, given their history.
>>
>>So, to all of this you responded "You have no clue what you are talking about." You took it to a personal level and your statement can't even be backed up. These are facts and opinions and there are shades of gray. I wish I had more time to discuss this - I really should be coding - but when I do take the time, I'm hoping for discussion without insults.
>
>MS's track record is they are always looking for the next best thing and they want everyone to abandon what they've done and start from scratch. They did it with VB and they are doing it with VFP.
>
>Why anyone would want to give them the chance to do it again is beyond me. There are things I can do with VFP that I could never do with .NET; and after investing so many years learning it, why should I start over with .NET just because MS says it's what I should use.
>
>I sure and the heck won't invest years of development time trying to convert apps that are working perfectly just so I can say they are written in .NET. In some circles, that would be a negative.

Well, let's say they did it 50% with VB and 100% with VFP . . . :~) . . . actually that should be . . . :~(

There are going to be people that just say "this has to be in .NET to be real and serious and modern and this and that." I can see that much more so with new development, but not for existing apps that are running well. The bottom line is companies don't want to spend the money again (though some will if the decision maker is big on having the latest glitz). They will have to do it eventually, but they want to get the most for their money and they want to have the time to plan out the move, so why shouldn't they keep using VFP for a while longer? ("A while" being defined differently in different situations.)
eCost.com continues to rip people off
Check their rating at ResellerRatings.com
Précédent
Répondre
Fil
Voir

Click here to load this message in the networking platform