Jay Johengen
Altamahaw-Ossipee, North Carolina, United States
Walter Meester
HoogkarspelNetherlands
General information
Category:
Visual FoxPro and .NET
Good post overall, Walter.
I spent a couple hours reviewing threads trying to find something from you that stated that .NET was bad and only Foxpro was good, but I ended up seeing that almost all of your arguments were about specifics on data handling and the amount of effort needed to create the same functionality in both languages. I was wrong on that.
I still feel that you do state your opinions as facts with regards to .NET, but agree that you have never said that a developer should always use Foxpro over .NET, rather that it is a personal choice and you would wait until it matures. We disagree on this. It's obvious to me that .NET is not vaporware and I feel that if a developer has the expectation that they will be using it in a couple years anyway, then they should go ahead and learn it now. Languages will always change and improve so waiting for it to mature just doesn't seem logical to me.
Previous
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only