Skip to main content

The FoxPro ecosystem

Neil Davidson has a great post on the Business of Software blog: The inevitable death of the ecosystem in which he notes how Microsoft is moving into arenas previously filled with their third-party partners and are now competing with them directly. The concern? "Third parties will start to leave the ecosystem and they won’t be replaced. "

So what about the FoxPro ecosystem?
With FoxPro being unleashed, we have a choice: leave it or tend it. The FoxPro community is full of great tools, some competing with each other while others are more complementary. But what is relevant here is that we no longer have to worry about Microsoft possibly coming out with a new feature that will hamper the existence of an existing tool. I recall when the new hooks for the report writer were first being talked about and there was an active discussion from Microsoft about how these changes might affect third party products.

Instead, we are free to build and enhance the great tools that we have been given and also come up with our own. And they can be similar tools or approaches.

Tod's post about automating project hooks referenced Rick Schummer's Project Builder tools - this was one of the first times I had even heard of this tool - because in the past, I've always just done it myself.

While there are other commercial tools available, developers are often a Do-It-Yourself breed. The FoxPro community has always had a good number of developers who are passionate about sharing their tools. Now's a good time to encourage other FoxPro developers to share their ideas and little tools they use.

Many will think now that Microsoft is effectively "leaving" the VFP ecosystem, FoxPro is a "dead product walking" (this is a term mentioned by Rafael Ruffulo in an upcoming article for ComputerWorld canada) - but ecosystems don't have to have major companies supporting it - as long as the other members of that community continue to support it.

Comments

Ed Leafe said…
"With FoxPro being unleashed, we have a choice: leave it or tend it."

There is a third option: reinvent it.

That's what Dabo is all about. Reinventing the magic that FoxPro offered, but in an open system that isn't controlled by some corporation whose interests don't parallel those of developers.

I want to keep developing great apps for my clients, and so I've focused my efforts on creating Dabo, so that others who also want to create database apps can do so without the shackles of Microsoft.

Popular posts from this blog

FoxInCloud Stats

FoxInCloud sent this link a while back about their statistics regarding visits to their site:

http://foxincloud.com/blog/2017/12/27/VFP-community-lessons-from-foxincloud-site.html



What's interesting here is the breakdown of people. Yes, I think it's understandable that the Fox community is getting older.

Another factor is the growth of the mobile and web environments taking over development. These environments really do push people towards the newer non-SQL or free SQL/hosted environments but more towards hosted storage options like Amazon and Google. A tool like FoxInCloud that helps MOVE existing applications to the cloud inherently competes with those environments.

But FoxInCloud also allows developers to extend their application further by giving them a starting point using Javascript and the basic CSS (such as Bootstrap). If you're not rebuilding your application from scratch, it's certainly a great step forward.

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 has its own …

The World of Updates Today

I just received an update for Office 365. It certainly includes some cool features - including starting in one environment and picking it up in another environment. In recent years, I've certainly enjoined the use of Continuity on a Mac and in fact, I feel spoiled being able to start a message in one environment (even Google) and then finish it off on another.  This has become some pervasive when we were reviewing our most recent backlog at a client site, a similar feature was added to the current workload.

But with web applications, the trend is to reduce the amount of software on a client machine. I used to have automatic backup for all of my machines (thanks Carbonite!) but these days, many of my machines don't need anything beyond the core OS and some basic applications. Certainly that's the feeling with Chromebooks and even the lightweight aspect of many iOS apps. The functionality is mostly in the cloud.

When you upgrade your system, you expect it to a big update. So…