>On what do you base that? I'm seeing more job offers, better press reviews. I >don't think a blanket statement one way or the other can be made for the next >12-18 months or so. I've personally seen two dyed-in-the-wool VB developers >suddenly go gung-ho on VFP after looking at VS6 betas.
Job offers are not an indication of a growing market. It might be in your neck of the woods. But, in the aggregate, VFP isn't even a blip on the charts. Better press reviews are just that. Will that help grow the market somewhat? Maybe. But I would not bank on it. Show most folks what VFP can do and they will be impressed. But, you will never see an exodus of VB developers going to VFP.
>I think you're position on this is weaker now than it was 6 mos. ago. But I >think it's still too soon to tell. I can think of no earthly reason why MS >would want to kill off such a versatile, OOP tool like VFP with 500,000 >developers.
Kill is a harsh term here. Look at ADO. This is a manifestation of VFP to some extent. Who says that the benefits of VFP translate into the VFP product itself? Just a thought....
>I do not disagree with the fact that VFP developers should have other skills. >But I think all VS developers should be at least conversant with one or more >of the other tools. It's bad to be a monolithic programmer in any language. >But, as I replied to Mike Feltman on another sub-thread, *maybe* VFP people >should become more acquainted with the data side (SQL Server, Oracle). After >all, VB developers are a dime-a-dozen while good DBAs are priceless.
A friend of mine just scored a 6 figure DBA job in Wyoming...WYOMING of all places.
Previous
Next
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