Skip to main content

How misinformation feeds FoxPro myths

So, Mary-Jo Foley calls VFP the "Rodney Dangerfield" child of Microsoft's solution and we wonder why there are mixed messages.

Steve Black emailed me this post where the supposed "Head of information technology" at an Indian company had to upgrade because "the software was not scalable as it had been developed on FoxPro".

Excuse me? The older software was probably not scalable because this guy, or the person who worked there before him, who had originally commissioned the software likely wrote it not to scalable. Yes, it was written in FoxPro - but it could likely have been written in Visual Basic.Net or Delphi or anything.

Applications are not inherently "not scalable" because of the platform but more because of the design.

Near the end of the article , the comment "Compared to legacy systems, which needed to be changed every six or seven years, SAP solutions are expected to prove effective for 20 to 25 years and beyond." - - "are expected to"???

SAP has only been in business since 1972 and while they have commendably only had 3 core versions but even so, R3 was only released in 1990 and I'm sure there have been upgrades since then. And is SAP written in the same language as it was back in 1979? I don't THINK so!

But why is it successful ? Because it was designed properly. (and I'm not an SAP expert - so I'm sure there are those who would say otherwise as well)

I've seen this before in lots of organizations. It sounds to me like the "head of IT" was likely someone who designed poorly written systems in the past, recognized it, became a manager who preferred "third party" vendors who would have to do the real scalable design work and then blamed their past failures on the product. Have you ever run across those kinds of people before?

By contrast, some businesses have been running the same FoxPro applications for years. One Canadian government agency refused to support FoxPro - their IT department thought that Paradox would be the next big thing - in the early 90's , even though their survey applications and many internal office systems were running with FoxPro. Their IT department changed and went to Visual Basic and SQL Server solutions. While the SQL database may have been fast, their programmers designed the new survey applications poorly and as a result, they went back to the ten-year old FoxPo program which wasn't just reliable but faster as well.

Craig Bailey posted this about the new MS certified Architect - this sounds like something that every head of IT should have BEFORE spreading mis-information.

General programming rule: It's not about the product - it's about the DESIGN!!!

I even recall hearing someone who worked at Microsoft say exactly the same thing. Internal systems at Microsoft weren't always written to be scalable and thus had to be re-architected.

Heck! I'm in the middle of re-architecting an older application to be more scalable and run under SQL Server. The older application used indices and filters to show information to a user. Could it run with a million records? sure! Should it? No! So the issue is one of how do you redesign it? In VFP or under another language?

In the most recent FoxShow (to be posted today I hope), John Petersen noted how he was interested to see how the arguments for FoxPro actually worked in a business meeting.

After reading this article and the mis-information spread around through it and other journals and by otherwise 'well-meaning" "IT experts", you can start to see a pattern. It isn't bad marketing that FoxPro is up against - it's ignorance, plain and simple.

How do you fight ignorance? By making BETTER applications (yes, I've said this before)

Some have noted that Ruby on Rails doesn't follow along the path of traditionally designed n-tier applications, choosing speed over architecture. Uh, tell that to 37Signals, the group behind Basecamp. Not sure how many users they have using it, but sure feels like a scalable application to me.

So once again, let me repeat: It's not about the product - it's about the DESIGN!!!

Comments

Randy Jean said…
Right on! Also, it's not just about the code design. poor database design (and management) will cause all sorts scaleability issues, too. I've been forced to take on SQL DBA responsibilities and I can tell you there are a lot of things to think about when dealing with enterprise databases that go way beyond how the application(s) are written.
Anonymous said…
I often found what get me excited when looking into an application is its design. An application built with old technology but with good design probably will last longer than a product with the latest technology but of poor design. Technology comes and goes and difficult to reuse and extend, design can.

Popular posts from this blog

Well, that explains CodePlex...

In a move that will be sure to anger open source (or rather anti-paid software, anti-Microsoft open source)  zealots, Microsoft is planning to buy GitHub . A year ago, I mused about why Microsoft would shut down CodePlex and how the world needs competing source code repositories to be strong. I'm not the only one per this Slashdot article  : "...   people have warned about GitHub becoming as large as it did as problematic because it concentrates too much of the power to make or break the open source world in a single entity, moreso because there were valid questions about GitHubs financial viability...." - Jacques Mattheij I will be interested in seeing this play out - whether developers jump ship or not. Have all the efforts Microsoft has made in pushing towards open source be seen as genuine or will all the zealots jump ship or maybe even attack? Microsoft's comment about why they shut down CodePlex referred to how spammers were using CodePlex. Well, GitHub

Attending Southwest Fox 2019 could change your life - Find out how

Southwest Fox is coming up in October and as I do every year, I spoke with the organizers Rick , Doug and Tamar on the FoxShow. Deadlines for Southwest Fox: Super-saver price (before July 1): $695 Early-bird price (before August 1): $770 Regular price (August 1 and later): $820 This year, I took a different approach with separate shows for each organizer but the main message is still the same : July 1st is their Go/No-Go date. Conferences don't talk about this very often. I don't think developers really question if Apple will hold their WWDC in June or Microsoft will hold their Build conference - but that's because those conferences are vendor-led. Southwest Fox is a community-driven conference - it's not driven by a company with an agenda. Listen to the interviews and you can hear how important each of the organizers feel the live connection between speakers and among attendees.

Virtual FoxFest - A New Way to Conference

If you haven't been keeping up with the news around the Fox community, the Southwest Fox conference has gone digital now showing up as  Virtual FoxFest .  At $49, it's a steal and a great way to learn some new ideas and get inspired. While the reasoning for this change is fairly obvious with the year of COVID - for me, this is something that has been a long time coming. I appreciate many people's needs for a physical conference but the world is very large and it's difficult to get people from around the world into a single physical location. I recently attended a single-track conference via YouTube (a Quasar conference). YouTube's Live stream provided a very handy way to watch, rewind and communicate with people online. While Tamar, Doug and Rick are still making decisions related to the streaming platform, there are lots of great options available. I'm really looking forward to it. The FoxPro community has also really felt its international roots