Stephen,
I guess you are correct. The good thing is that at least in this type of
marked M$ have some competition which obviously results in all the competing
products evolving into better solutions.

The biggest problem both of them have at the moment is not the
infrastructure but outsourcing. In that 90% of the devs have been outsourced
to people from Asia because of cost. Unfortunately it would seem that
although they are technically qualified they have little if no practical
business experience which has resulted in massive project delays and
associated cost. The original team were made up of about 50 European and
Australasian devs who although expensive were very good. 

The workforce has now more than doubled even though the costs probably are
less in total but there would seem to be a total lack of "cohesion" and work
ethos within the team. I guess that this is the result of short term "cost
saving" when it comes to recruiting and shows that whatever platform you
choose for a project then it will be useless without the people who
understand the logistics and infrastructure adequately.

Still, I digress here as we are getting away from the hardware discussion
but it does beg the question you posed regarding the acceptance of .Net
technology by VFP devs. My take on the situation has changed radically over
the last 6 months and in fact since .Net 3.x which has now matured into a
stable platform with superb development tools. I still think the whole of
the .net framework is far to big which doesn't halp when you are trying to
learn not just the language but also the framework but once you have
mastered it you can usually do many more things than in VFP - and with less
effort which look prettier as well. I still just wish that M$ would/should
have incorporate the ease of data handling from day 1 into both c# and .net.

Currently I am using the Strataframe framework to build .net applications in
c#. For those of you not in the know it was developed by ex VFPer's and this
shows. Data binding is a breeze and you can use the data based logic of VFP
when designing applications so tha meny years of VFP rigour are still
useful. All in all a recommended product and reasonably priced.

Dave Crozier






_______________________________________________
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/7648f09b07c54434a69741326b320...@develop
** 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