Skip to main content

MS VFP starts its departure - are you ready for community-based VFP?

Looks like Craig Bailey got the first link up on this but every FoxPro developer needs to see it here

What does it all mean? Well, yes - no more "Microsoft" VFP after Sedna and SP2 - although it is supported through 2015.

But perhaps more importantly - all of the Sedna code is being released into Codeplex - so we can all extend it further. This is a very strong point as it means we, as FoxPro developers, can continue to expand on the tool and make it better.

There will always be areas that we might gripe and complain (for example, why can't we get a pre-processor at compile time?) - but we can find ways around it. Myself, I would love to see them release more internals to the code under a similar license but I don't think that will happen.

However, if you've read the other Craig's blog of late, you'll see that Microsoft is now switching whole-heartedly over to a 64-bit platform, which VFP was never going to support. Whether this is a good move for Microsoft or not, who's to say. Software development is changing and it's all about choosing the right tool.

Most businesses won't be changing to 64-bit anytime and until they do, VFP is still one of the best tools around for data access. And as long as MS continues to improve its Vista compatibility with Sedna (which I'm still not even that fond of), then it's still the right tool for many data-based 32-bit applications and as the VFPX projects show, there's no shortage of what you can do with it.

I still want to find other ways of baking new stuff with VFP, be it linking with open Web APIs, other databases and more. It's not the tool - it's what you do with it and with FoxPro, you can and still will be able to do a lot.

But yag, thanks for letting everyone know.

powered by performancing firefox

Update: Mary Jo notes it also here.


Garrett said…
Ok, it's official: I am chopped liver. :-)
Andrew MacNeill said…
Nonsense. Now we can feel good about really promoting FoxPro without having to worry too much about MS coming down on it.

But nice picture there! :)
Garrett said…
I meant that I thought I had blogged it first, but nobody noticed. Then I remembered the International Date Line. :-)

Popular posts from this blog

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 distinctions I…

Security in Windows 10

 discusses some Windows 10 privacy settings and their implications.

"Finally, we will access, disclose and preserve personal data, including your content (such as the content of your emails, other private communications or files in private folders), when we have a good faith belief that doing so is necessary." "In other words, Microsoft won't treat your local data with any more privacy than it treats your data on its servers and may upload your local data to its servers arbitrarily"
I did a quick install on a VM choosing the Express settings. When I fully deploy this on a real workstation, I will likely choose to wade through all of the individual pages, as David recommends.

Of course, losing one's privacy is nothing new - it's happening all over the place (despite Santa Ana's police force's lawsu…


I'm not TRYING to be "fanboy-flame bait" but what I saw yesterday was a typical "Do it this way, now do it this way and then we'll go back to this way" all over again.... a move similar to what Microsoft does to developers on an ongoing basis.

Remember the first iPhone? Smooth and curved, at least as far as it could be back then. I still pull out my 3G and can see the curves on it.

Then the 4 came out and "boxy" was all the rage. Everything should be "tight with corners"

Now iPhone 6.... smooth and curvy is back. Granted I don't have the actual device yet, but that's the message.

Guess that means the iPhone 8 will be back to boxy.

And honestly, Apple Watch is not worth "one more thing" --- especially when everyone knows it's going to be shown. "One more thing" would be something no one saw coming.  The device itself ? Very interesting and yes, definitely lots of potential but "one more thing" wor…