2009/4/10 Ricardo Aráoz <[email protected]>:

>> How did they kill it?  Is it no longer working?  Or has the quality of
>> other developer tools open source or non lured developers away from
>> VFP?
>>
> Sorry, you are absolutely right, they didn't kill the fox. Everybody
> knows that! My bad.
---------------------------------

I am sorry but it is up to people like you to make the great software
that customers want to purchase.  What it is made with is secondary to
truly innovative products.

>>
>>
>> OK, I'll bite.  What innovation do you really need?
>>
>> Would you expect the owner of FoxPro to in essence rewrite it to
>> achieve the new features you want / expect?  This would take into
>> consideration the 2 gig limit and other bla bla bla.
>>
>> If they did that would that bring people flooding back?
>>
> Let's see, if there is NO chance that people will come back to the fox
> then. Why don't they give the code to the public? Why don't they let
> OTHER people keep developing it instead of discontinuing it?
> Oh! I know! It's because they want to present quality in the developer
> tool space.
---------------------------------------------

What would you do with reams of C code?  Would you change the base
engine to get past the 2 gig limit?

Outside of that true limit what else is M$ not doing for you?

-- 
Stephen Russell
Sr. Production Systems Programmer
Web and Windows Development
Independent Contractor
Memphis TN

901.246-0159

_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: 
http://leafe.com/archives/byMID/profox/[email protected]
** All postings, unless explicitly stated otherwise, are the opinions of the 
author, and do not constitute legal or medical advice. This statement is added 
to the messages for those lawyers who are too stupid to see the obvious.

Reply via email to