MARKETING OF VFP
From: Boudewijn Lutgerink
marketing of VFP
marketing of VFP
Visual FoxPro 8
Wednesday, April 02, 2003 9:42:59 AM
This message was rated by:
As a VFP programmer I am indeed worried about the fact that the MS marketing on VFP stinks.
Any possibility I see I will use to "tell the world" about VFP.
Today I found an article on
about the diminishing of .NET another blunder of MS marketing.
I used that to send the following reaction, I just wanted to share this with yer'all.
In case any of you might see possibilities to "tell the world" about the fox please take your chance and do so.
I do not foresee any increased marketing efforts coming from MS now that they did shoot themselves in the foot once more.
Any idea in this context is welcome.
Indeed I think, as a developer with 10+ years experience, that from the start MS never gave any good thought about what to achieve with .NET.
I made it thus .NJET for me.
Comes to mind what my late father learned me as a kid: "Something you cannot explain in clear and concise words is not really thought through."
In my not so humble opinion, I think this .NET thing falls in the same category as developing application based on a browser interface.
Browser interfaces simply miss the immediate interaction with users that desktop interfaces do have.
The argument that in this way (using browser interfaces) databases anywhere on the world could be contacted is overruled with the use of MySQL, the ODBC
driver that ships with it makes it possible for any development tool to contact a database anywhere on the world.
Whatever people say about MS as a marketing machine, the marketing folks at Redmond seem to forget that MS has indeed one extremely stable development
tool that is quite under-estimated, in all the fuzz around cool, fantastic,hot (or whatever you can come up with) .NET. I am talking here about MS
In its 8th version already VFP has developed from a tool that has an xBase background to a tool that can be used to handle data of any source with ease
at an unbeatable speed and with good OOP implementation. Big applause for the VFP programmers team in Redmond for their efforts!
Comparing development of applications in VFP vs the same activity in .NET is like comparing the speed of a ferrari (VFP) to a T-ford (.NJET).
Only about 25% of the time is needed to develop an app in VFP compared to .NJET.
CEO's and decisionmakers in any type of business should be clear in their desires for quick and flawless development of the apps they need.
Another encouraging fact is the attempts of mr Paul McNett (
) to make VFP work on the linux platform using Wine. He is making incredible
This shows that the development efforts of those programmers using VFP is not restricted to the windows platform but can be extended to other, fast
growing platforms, as well.
One of the main reasons for using the predecessor of VFP, FP(W), was that this tool could develop code for Windows, Unix, Dos and MAC.
With these efforts those times seem to return once more.
The datacentric language of VFP and its OOP implementation make it a tool of choice for any developer who has a desire to develop applications fast.
The possibility to implement any COM component, developed in eg C++ or VB, with ease and the fact that apps developed in VFP can serve as COM components for
other languages make VFP the flexible tool any developer is looking for!
Experience is the knowledge you get immediately AFTER you actually needed it...