Whil, You talk a lot of sense! :o)
You wouldn't believe how tight my market is. If they could get away with using an app for 30 years on the same pc they would! Obviously hardware will die in that time, but hopefully my users will have backed up my software and data and they can restore, install the runtime setup and continue on their merry way. VFP should run after 2015 but there are no guarantees from Microsoft to say that it will. If they can't guarantee it then I have to plan that it won't work, If I don't then I'm going to be in big trouble with my customers. Rob -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Whil Hentzen Posted At: 09 November 2007 19:27 Posted To: Profox Archive Conversation: [NF] Fingerprint Scanners Subject: Re: [NF] Fingerprint Scanners Robert Jennings wrote: > In 2015 M$oft will stop support for VFP. > > At any point after that date they could make windows not support VFP. They 'could', but will they? Any more than they 'made' Windows not support Fox/DOS? What would be the point of expending that effort? What's the MSFT business case for paying someone to consciously make that happen? Picture some guy walking into their manager's office and saying, "I need to budget for two programmers for three months to make sure that a database product we used to sell ten years ago doesn't work with our upcoming version of Windows." What manager is going to greenlight that? :) > My customers (and I expect your's too) will not want to purchase VFP > apps in case the lights suddenly go out due to an automatic update or > son of vista. Some of them have already voiced concerns over VFP but > I've told them I'm migrating to Python or similar. Sounds like a plan. > One of these VFP run on dot net would be good but what happens when > .net goes to 3 or 4 or 5, will it still work? Will those .net 1.0 apps work? 1.5? 2.0? > We're seriously looking at Python & WxPython to replace Foxpro as it's > cross platform and I'm not tied into having to re-write every line of > code every 15 years! The only point of dabo that scares my is that the > framework is there. Will I be channeled down to their way of thinking > for creating my apps? At least if I write from the ground Up I have > total control over everything. > > The life span of my software should be at least 30 years. That's how > long a Ship can last, so my software needs to as well. As long as the computers also last 30 years, right? :) Seriously, are you saying that you're going to write your app, put it on a ship, and that's that - your job is done? The business that your customer will never change for the next 30 years? I dunno, I think that's kind of an unreasonable expectation. That said, MSFT's expectation of you rewriting your software every time .NET gets bumped isn't unreasonable... it's just plain stupid. There's gotta be a middle ground in there somewhere. With Python/Dabo, you have access to the source code, so you're not hosed as if you were with a proprietary toolset. Whil [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.
