Skip to main content

Vienna will support 32-bit: Even longer life for FoxPro applications

I'll admit it - when Craig has talked about the move to 64-bit in the past, I've agreed with him on it. Microsoft has said numerous times now that they are moving into exclusive 64-bit territory. With all the calls from FoxPro developers wanting VFP to go 64-bit, the amount of work required to do this was always cited as being a reason for not doing any upgrades along this path. Yes, VFP would always run in 32-bit compatibility mode on a 64-bit processor but otherwise, it's not going to take advantage of the next generation of processors. This suggested to me that realistically, 32-bit apps have a future life-span of 10, maybe 15, years.

But this article from ZDNet, Next version of Windows: Call it 7 has a VERY interesting line: "

Like Vista, Windows 7 will ship in consumer and business versions, and in 32-bit and 64-bit versions."

While FoxPro is supported from Microsoft until 2015 but with basic support ending in or around 2010, this means that the next version of Windows will be out around that same timeframe, which would suggest that FoxPro would also be supported under that platform. (as in "runs under Vienna" as opposed to "works with Vienna" or "Certified for Vienna")

It's a curious statement - and maybe someone was misreading something - so if I/they am/are, please clarify.

Most applications these-days are compiled as 32-bit, but more importantly, most of these applications all typically rely on the standard Win32 API. Yes, VS2008 and Silverlight all promise to bring around the wonderful new world of WPF to everyone but real application development on these platforms (as opposed to very cool and fun tutorials) still seems a bit far out there.

Someone recently compared the current tech/dev world to the OS world in the early 90s, when no one knew what the next "big" thing was going to be.

I know of a few large organizations that only just recently moved to XP (from 2000). So yes, there will be the organizations that will continue to move forward and pushing the development edge but they will also be taking a side as to which platform they are supporting. What side the majority of the world comes down on may be a moot point if webware applications (like Coghead - boy that is fun to build with!) continue to grow.

To me, it seems like a good part, if not the majority, of the Desktop world will still be living with 32-bit apps, even though their processors will be 64-bit, for quite a few years to go. In older shops, you may have seen workers flipping between their Windows apps and their 3270 emulation windows. Even today, you see users flipping between Mac to Windows or Linux to WINE apps, etc - all from within their own computer.

The one common denominator that I see on almost all of those platforms? The Browser. Hmmm...maybe Parakey does have something...




Powered by ScribeFire.

Comments

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

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

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