From the blog:
Quite surprisingly, a lot of people who are highly regarded in the VFP and software development community are looking at this as generally positive news. Myself, I'm a bit dubious. Working for a software shop that uses several various technologies (VFP, Java, .NET, PHP, BEA, Oracle, SQL Server, etc.) there is an expectation that we look to "future proof" our work as much as possible. Overall, the decision to use VFP on many, many successful projects has been a very good thing. But now what do I recommend? Of course we who use VFP every day can attest to it's technical and RAD capabilities, etc., but many of our corporate clients want to know that if we go away, or I get hit by a bus, etc. that they can find someone to support their apps. Last time I checked, there was not a whole lot of VFP talent in South Bend, Indiana.More:
It’s sad because as a software engineer, even when I know VFP may be the perfect fit for a new project, I'm also a consultant and I have to be pragmatic and may not recommend new projects use VFP. Maybe it’s because I’m just getting tired of constantly fighting the negative spin and this news might make the fights harder to win.More:
There’s nothing worse than implementing a successful project only to have the decision of the development tool questioned over and over, sometimes several years later, every time a new person (or manager) gets involved with the project. Fortunately, I have clients that actually look at the results and know when to dismiss the undeserved negative remarks about VFP, but who knows about the next potential client….
No comments:
Post a Comment