Skip to main content

Ken Levy: Plans for Visual FoxPro beyond version 9.0 coming

Well there's an old adage that ends with "you just might get it..." and Ken, while not spilling any proverbial beans, lets us know "the Visual FoxPro team has already started working on enhancing Visual FoxPro beyond version 9.0"

But what's also important is that he warns "People should keep in mind that our goals and focus is on how Visual FoxPro apps run in 5+ years rather than on specific VFP IDE, engine, and language features."

Well - there's a wealth of suggestions on the Wiki but...

Hmmm....5 years.....MS has already made a very large push towards 64-bit and it reminded me of a comment that Steven Black ( I thought) had made on the Wiki (but I couldn't find it) that seemed to suggest that VFP might be very ripe for a transition to a 64-bit environment.

(Update: from Ken and the VFP FAQ:
Q: Are there plans for Visual FoxPro to support 64-bit versions of the Windows operating system?

A: No. While Visual FoxPro will remain 32-bit and not natively use 64-bit addressing, it will run in 32-bit compatibility mode. Visual Studio 2005 will support creating native 64-bit applications.

Still - it looks like the Fox will be around for a few more years.

Looks like June will be very exciting. Can't wait to see that Road map, Ken!

Ken Levy's Blog : Plans for Visual FoxPro beyond version 9.0 coming in June

Comments

Popular posts from this blog

Merry Christmas

Whether you celebrate now, have already celebrated your past holiday, are planning to, or not, I hope you find yourself surrounded by family and those you love during this holiday season and are able to remember fondly those who are not with you. We often find ourselves buried in work, or too distracted by other problems, to share and remember a few moments with those closest to us. So many of us are separated by huge distances, we often find it easier to focus on those who are out of arm's reach yet so easy to connect with online, instead of those who are right beside us. So do yourself a favour, put down the keyboard (stylus, mouse, etc) and spend that time. I know I will. Merry Christmas. Powered by ScribeFire .

From Writing to AI: the pattern repeats itself

When I was ten years old, my dad bought a computer and, thanks to an advertising supplement in a Superman comic I read, it was a TRS-80. A month later, he dragged the entire family (my mom and brother were not the most enthusiastic) to a class at Radio Shack teaching how to use microcomputers. At the time, I understood why my mom wasn’t that excited: the computer was yet another gadget in the house. But today I find it fascinating. My mother went to Vassar in the 50s. She learned how to type — not a common skill at the time — but it opened doors. Her ability to communicate effectively led her to a career in adult education and later communications work with the CBC (Canadian Broadcasting Corporation). This isn’t a nostalgia post. Today, the ability to use artificial intelligence, be it through Copilot or simply writing the right prompt, is becoming a critical skill. But is it really that novel? In the 1500s and 1600s, the printing press gradually made reading accessible beyond cler...

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...