I guess the only thing for it is to write everything in C Correct me if I'm wrong, but aren't all OS written in C? You should then be able to compile your app to run in every OS.
Problem is C doesn't have native Database handling. 4GL's enabled most of us to deliver products to the world at reasonable cost. VFP allowed us to deliver excellent database applications as it was and is a 1 stop shop. You can do everything you want to in VFP. The problem is, there is no sure fire system that we can put our hands on our hearts and say, Yes, in 2050 this 4GL programming language will still be around and running on OS's out there. If you read all these "RE: Another Life after VFP thread?" mails most people are looking at something different, some .Net, Python, Dabo, Lamp and others I cannot remember but are in the posts. Every single option has it's drawbacks. VFP came from good stock. It allowed access to Databases (DBF's) I can open a table that I created in dbase in 1992 and I'm sure you all will be able to go back further. I know that we can run XP in a Virtual PC well into the future, but will customers want to do that? I think not. We won't be allowed to run a VFP on Linux and the replacement to Vista might have removed support for the VFP runtime. 2015 isn't that far away in the scheme of things specially when a rewrite is on the horizon. Robert Jennings -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ed Leafe Posted At: 03 April 2007 11:52 Posted To: Profox Archive Conversation: Another life after VFP thread? Subject: Re: Another life after VFP thread? On Apr 3, 2007, at 4:58 AM, Robert Jennings wrote: > It's just, I'm going to have to give my customers a roadmap of where > we are going. Otherwise they may loose confidence in us as a company > and go elsewhere! > > Just imagine that Microsoft write Office 2007 in C# > > Now Microsoft remove support for C# from Windows. > > Now Microsoft have to re-write office 2007 in Java from the ground up. > > Office will be about £1500 a copy and people will not buy it. That's exactly why I feel so strongly about investing my development efforts into open source tools. Many of the sycophants here like to think it's because I "hate" Microsoft, but it's actually because it just makes good business sense. Microsoft, or anyone else for that matter, can't "remove support" for Python on Windows. They don't control Python. Even if the primary group developing Python decided not to support an OS, the source is available with no license burdens, and there would be enough financial incentive for someone to make it compatible. -- Ed Leafe -- http://leafe.com -- http://dabodev.com [excessive quoting removed by server] _______________________________________________ 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.
