Skip to main content

Visual FoxPro History at Microsoft

Ken Levy has an interesting post up on his MashupX site since early last month.
Ken Levy's Blog _ MashupX Visual FoxPro Strategy at Microsoft

The post goes into some fascinating details as to the history of Visual FoxPro at Microsoft. Most of it is well-known or obvious (making VFP.Net would break backward compatibility - which is what MS did with VB.Net as well)

I guess more details can be shared now - when VFP 9 was released, "the amount of sales for all versions of VFP combined annually was less revenue than Microsoft sales of Visual Studio in only one day"

It would be interesting to know however if some of those companies who were out there working on a VFP-like language in .Net were "persuaded" to stop their efforts, as some have suggested in various forums.


Well worth the read. The FoxPro community is what keeps VFP alive (thanks to VFPX and other initiatives) - and there were some members of that community inside of Microsoft at one point.
As he notes at the end "Only developers who have used FoxPro really appreciate it for what it was and still is."


Comments

FoxPro said…
Very much true, I have been using FoxPro for almost four years and I like the way it is compared to other tools. Even though I am tempted to earn other language to cope with the user client request.
July 5, 2011 at 11:50 AM
Post a Comment

Popular posts from this blog

Blogs and RSS come to Microsoft.com

MS has just introduced their portal and it's pretty comprehensive. Nothing quite like learning that some people use AIM instead of MSN messenger, or that there really may be a need for supporting 4 monitors ( Cyrus Complains ) However, it's really a great sign that MS is serious about supporting the blogging community which seems to have um, exploded in size in the past year. Blogs and RSS come to Microsoft.com
1 comment
Read more

Elevating Project Specifications with Three Insightful ChatGPT Prompts

For developers and testers, ChatGPT, the freely accessible tool from OpenAI, is game-changing. If you want to learn a new programming language, ask for samples or have it convert your existing code. This can be done in Visual Studio Code (using GitHub CoPilot) or directly in the ChatGPT app or web site.  If you’re a tester, ChatGPT can write a test spec or actual test code (if you use Jest or Cypress) based on existing code, copied and pasted into the input area. But ChatGPT can be of huge value for analysts (whether system or business) who need to validate their needs. There’s often a disconnect between developers and analysts. Analysts complain that developers don’t build what they asked for or ask too many questions. Developers complain that analysts haven’t thought of obvious things. In these situations, ChatGPT can be a great intermediary. At its worst, it forces you to think about and then discount obvious issues. At best, it clarifies the needs into documented requirements. ...
Post a Comment
Read more

Programmers vs. Developers vs. Architects

I received an email this morning from Brandon Savage 's newsletter. Brandon's a PHP guru (works at Mozilla) but his newsletter and books have some great overall perspectives for developers of all languages. However, this last one (What's the difference between developers and architects?) kind of rubs me the wrong way. Either that, or I've just missed the natural inflation of job descriptions. (maybe, it's like the change in terminology between Garbage man and Waste Engineer or Secretary and Office Administrator) So maybe it's just me - but I think there's still a big difference between Programmer, Developer and then of course, architect. The key thing here is that every role has a different perspective and every one of those perspectives has value. The original MSF create roles like Product Manager, Program Manager, Developer, Tester, etc - so every concept may pigeon hole people into different roles. But the statements Brandon makes are often distinction...
12 comments
Read more