XBase Myths Debunked

Filed Under (Random.scribbles, Visual FoxPro, work.BLOG) by WildFire on 14-06-2005

Four days of not having checked my email and I'm bombarded with 'man'-enhancing-related spam, pirated-oem-software-buy-me-buy-me-lists and netsky-infected zip files this morning.

Behind that file of crap, I did find a link to this article (XBase Myths Debunked) from the ProFoxTech list.

The article is maybe almost a year old, but give it two more years and what it is saying will still probably be true. Allow me to extract some snippets.

Contrary to what we are all led to believe by the computing press, hype and the mighty marketing dollars of the large software companies it is 'Applications' that drive the use of IT in companies of all sizes. Yes 'Applications', not languages, operating systems, development tools or database systems. It is these applications that can make or break a company. The ability of the application to perform or respond to user requests quickly and reliably is of paramount importance to the survival of any organization.

Exactly my sentiments. And here I am thinking that Visual Foxpro is the last XBase standing. That it is the last one which understands how to handle data and records and speed and efficiency and all.

Here's more. (Beakman hear this out)

The IT landscape has been fed with many "Bait and switch" tools, languages, and other technologies for as long as I can remember. If we as developers were to jump on each and every bandwagon that was raved about in the press and on the web, we would never complete any projects. Ever!

Reminds me of a small portion of Joel Spolsky's Fire and Motion article:

Think of the history of data access strategies to come out of Microsoft. ODBC, RDO, DAO, ADO, OLEDB, now ADO.NET - All New! Are these technological imperatives? The result of an incompetent design group that needs to reinvent data access every goddamn year? (That's probably it, actually.) But the end result is just cover fire. The competition has no choice but to spend all their time porting and keeping up, time that they can't spend writing new features.

Innovation is good. But if profits play a major role in its push, and reliability and productivity are sacrificed then it is bound to mate with some green germs down the drain.

No offense meant to the green germs.