Ed,

I hear you!

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.


Robert Jennings


 


-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ed Leafe
Posted At: 02 April 2007 21:26
Posted To: Profox Archive
Conversation: Another life after VFP thread?
Subject: Re: Another life after VFP thread?


On Apr 2, 2007, at 12:30 PM, Robert Jennings wrote:

> Your thoughts on all of the above will be appreciated.

        I wonder if they would guarantee that apps written in .Net today will 
run on the current OS in 2015.

        My feeling is that if your app is working, there is no need to panic 
and abandon all that good, solid code because they finally made official what 
many of us have sensed for quite some time. Given the number of really smart 
people who use Fox, I'll bet that even if Microsoft doesn't do it, someone will 
figure out a way to make VFP run on future OSs. Remember, the fast CPU fix 
didn't come from Microsoft, but it enabled old Fox 2.x apps to run on hardware 
well past the lives of the products.

        Also, just how much faith would you put in a promise from Microsoft?  
My feeling is that as long as it doesn't hurt their bottom line they would keep 
it, but they'd have no problem "writing it off" if conditions changed. I 
learned that after the VFP/Mac beta, after spending a lot of time getting 
things working and tracking down bugs, they released a known buggy product and 
then refused to commit to patching the bugs they acknowledged just a few months 
prior. IOW, their word is as good as their business cash flow.

        Personally, I would begin planning for a transition to something that 
will take you through the next decade or two. That's a long time for any 
product, but it's also precisely why I think that .Net is the worst choice you 
can make. In the mid-90s Microsoft was strongly pushing their COM model as the 
way to go, only to dump it a few years later for .Net. There is no reason not 
to think that in a few years they'll come up with yet another trendily-named 
product, and tell you that unless you move all your code to this platform, 
you'll be a dinosaur.

-- 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.

Reply via email to