Don’t Let Software Die ~ Chris Pirillo
Interesting post regarding TuCow's decision a while back to stop updating Blogware. It reminded me a little of VFP in that it's a company that has decided to stop updating one of its software packages.
Chris' comments on the letter:
>> What worries me most about building communities on closed platforms is that as soon as those platforms change direction or stop innovating, you’re locked into a toolset that has nowhere to go but down
Whoa! Does this sound like VFP and FoxPro? Read on...
>> Tucows has given absolutely no indication that they’re interested in opening the platform at all - leaving you in more of a no-win situation.
You can't fault Microsoft for not wanting to open up the VFP engine - as that has given a lot of its other products some definite improvements but the re-licensing of the xBase components certainly does show that they were interested in not killing it outright. Indeed, I think Microsoft deserves some kudos for a lot of the openness they have shown recently (VSX, etc).
Before you criticize my "blind support", of course, it's for the good of their business. Why else would someone do anything? You want developers to be using the Visual Studio Shell, to make their development "home" beyond everything else. But it's great that they have opened it up to let others create their own environment within it.
>> My “continued support of Tucows” is completely contingent on what they decide to do with Blogware now… aside from abandoning it. Don’t let software die, please? If nobody wants to pick up the ball and run with it, at least you would have given them the opportunity to do so.
At a recent Microsoft event, I ran into some developers who offered the comment "When was your last version?" (or something to that effect). My response? "If you're waiting for Microsoft to be the only one to improve a product's offering, then you're in the wrong business". That isn't a slant against Microsoft - but rather against those who would say "well, it can't do it out of the box so therefore, I'll wait for it to do it INSIDE the box".
Microsoft has offered FoxPro developers this - "you can't have the rubber that makes up the ball, but here's the ball - run with it."
So when people ask what's the latest version of FoxPro, I simply say "VFPX". There has been and will always be more innovation inside a product's community than just what is inside a product vendor's corporation. And that is good for the entire community. If you ever get into a situation where the only people offering new features or uses for an (existing) product is the actual company making it, be forewarned.
(note: I say existing because obviously that is very often the case for startup products)
The only thing we have to figure out is how to ensure people can continue to purchase VFP proper...can a third-party organization possibly get a "distribution license" for perpetuity?