Mike’s post about the “Business Decision” to kill VFP reminded me I had this older post that was still stuck in drafts. As Mike says “Microsoft was hell bent against dynamic languages. But now? Microsoft is investing in creating versions of Python and Ruby for .NET and of course already has Jscript. If these dynamic languages can be developed for .NET, there’s no reason VFP can’t be ported to .NET.”
I recall a time when the promoted disadvantage of FoxPro applications was that it required a separate runtime. “True applications don’t need additional runtimes” was the mantra of many a developer, usually C at that time, but then when Visual Basic received native support as well, its developers joined that group (even though their support typically consisted of bundling the runtime directly with it).
Of course, it also made it easier to distribute VB applications when standard Office applications installed it by default as well. I even recall some discussion among FoxPro developers that all Microsoft had to do to make FoxPro applications more “acceptable” was to include the VFP runtime as a standard part of the OS.
No one makes those statements anymore. After all, Java requires a runtime (thankfully typically installed with your web browsers), DotNet requires a massive runtime (but since Vista, WinXP SP2 and Win2K3 all install it by default, no one notices) and now, Adobe’s work with their platform independent Apollo will also require a runtime.
At least Adobe calls it a runtime – Java’s Virtual Machine and DotNet’s Framework all mask the fact that it’s exactly what users have had to do with most applications for years. No one complains about this anymore.
But as FoxPro developers, we were often the ones who got crucified for having a separate runtime, until it become fashionable to do it.