What are the main forces that must be considered and resolved?
Recall the flow of any well structured argument: Problem => Factors to consider => Options => Recommendation (Analysis) => Do this for Implementation (creativity)
This topic relates to Open Letter To Microsoft, an issue in February 2001
(Please refactor mercilessly)
Factors to Consider
- Microsoft did not, does not, and probably never will aggressively promote Visual FoxPro for enterprise development. We don't expect this to change. This doesn't mean we agree with this view. Our collective works clearly indicates that VFP is vastly more capable than the megre credit its grudgingly given by Microsoft.
- Microsoft did not, and evidently still does not educate its rank-and-file about the strengths of Visual Foxpro. Nor does Microsoft publicly elucidate its commitment to the Visual Foxpro development community. We expect this to change. Moreover we can show that it's sensible to do so. We offer to help to get this done.
- Microsoft has supported the VFP community extensively on a technical level. You have provided VFP with facilities and improvements that have led the market more than once. However the same is not true for public support in the form of marketing, promotion to potential clients, and by speakers at regional conferences. Casual observers are forgiven for believing that VFP is not a Microsoft product at all. Take Microsoft Press, for example, which stocks or sells no Visual Foxpro titles whatsoever. This is a travesty, and this needs to be rectified. If there is any truth to claims of support for Visual Foxpro, it will be. This is your litmus test, Robert.
- This is a period of great upheaval for Microsoft products; massive changes are afoot. Visual Foxpro is a sheltered harbour in these choppy seas. It is a stable, mature, proven and performing platform that, regardless of the acceptance of .NET, provides many of .NETs capabilities now, albeit with third-party tools and support. Visual FoxPro is a great place to be right now. It's getting more capable, more stable, and faster. This you can take to the bank.
One initiative that could prove beneficial to this argument and IT in general is to invite Gartner Group to present a better alternative to VFP instead of just putting the language down without thorough and provable representation. ChrisJohnson
Michael, I don't believe that promoting VFP will assist MS's bottom line through more sales. If developers leave VFP, where do they go? I'd warrant a good number go to VB. Where is the loss for MS, or the gain if people stay in VFP- especially if both are in the same visual studio? Surely bottom line can only improve if people migrate to VFP from (say) Java or cobol, who would not have gone to VB; or if people leave VFP and move to (say) Java or powerbuilder.
An alternative important "gain" comes if another group of developers with a reputation for independence and not swimming completely with the MS flow, agrees with MS's direction and has sufficient experience with object orientation and the like to argue about it.
We don't need to debate, but "gut feel" tells me we're wasting our time trying to convince MS that promoting VFP will earn more money for them.- John Ryan
You could look at it this way too, with VB/VC.NET all their desktop and shareware developers have to look for a non- over the top distributed environment. If they can get netted up (pun somewhat intended) by VFP there is revenue for them and not for whereever they were headed, most likely Delphi. I think alot of things in VFP have to change before that happens though. Like OO Menus, Reports and Data, and teh overall environment for one. -- Mike Helland
Open Letter Draft Guidelines
Open Letter Bogus Counter Arguments
Open Letter This Could Be AWaste Of Time
Open Letter Stuff Thats Probably Too Far Out There To Pursue
Open Letter Problem Statement Section
Open Letter Options Section
Open Letter Recommendations Section
Open Letter Implementation Section
Category Open Letter To Microsoft
( Topic last updated: 2001.03.01 12:09:48 AM )