Skip to main content

Comments on VFP Awareness Editorial

Message
Here's a note from David Dee on my recent editorial in FPA about increasing VFP Awareness. Please add comments
 
 From: David W. Dee [mailto:dwdcatalyst@ij.net]
Subject: VFP Awareness

I just read your comments about perceptions of VFP as a development environment.  It's something  that concerns a lot of people who've spent (years) using it and developing skills.
 
The direction that Catalyst Consulting has been taking is that VFP doesn't offer many advantages   when it comes to WWW development.  However, in a enterprise environment using Citrix and something   like HP's new blade-servers, VFP is absolutely perfect.  Citrix provides connectivity at a distance, while
the new blade-servers (and their competitors) essentially offer a WAN\LAN computing environment where   VFP excels.
 
Besides it's overall excellence as an object-oriented development environment, the VFP database engine   can run on each client node - potentially decreasing the load on central server resources by doing more of the database work at each node.
 
For these reasons we think that a mix of VFP on the client-nodes as well as a hefty central SQL Server database may be the best (certainly the most underrated) enterprise development environment out there.   "Client footprint" really depends on what resource you're trying to optimize - if the real bottleneck is throughput to SQL Server, then VFP has the capability to minimize that footprint.
 
I really think that the VFP community would do well to try and make contact with Citrix and maybe HP and   other hardware vendors out there who are starting to offer alternatives to the HTTP:\WWW low-bandwidth world   that we've been stuck in for so long.
 
I'd be glad to hear any reply or thoughts you might have along these lines.
 
Best Regards,

David Dee
Catalyst Consulting
 

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