Future of (your) Development Lies in You, Not Microsoft
From the Blog:
I also wanted to make a comment about Microsoft's development approach. They have a lot of great tools and amazing people. But one thing that has frustrated me and other developers is their need to continually RE-PACKAGE or re-design development approaches. And this isn't just with FoxPro and VFP. This is about development architecture. In the beginning was Client-Server, then DNA, then COM, then COM+, SOAP, etc, etc. You used to access data via ODBC, then ADO, now ADO.Net and now LINQ. You could build forms with VB, then in Visual Studio 2003, it was WinForms, and now it's WPF/E. And most of these changes in strategy have come out all within the past 10-15 years. This isn't to say they aren't good or great. But many of these changes weren't easy to bring about in existing code - they required redesign. The developers who jumped on one technology's bandwagon then had to be prepared to jump over to the next new one when it came out, because it was "going away".
From the comments:
VFP will live as the desktop development lives!...BTW, I keep an eye on .Net and I hope until 2015 Microsoft to have a VFP equivalent product for the job.
Another:
...the one shining star in this otherwise dark last few days is the potential that placing VFP in the open source community has.
It also has a potentially huge downside, but, honestly, I don't know if it could get much worse, and, if some of the folks who've been working with the internals for years hang in there, it could be an entire 'breath of fresh air' for the future of VFP.
No comments:
Post a Comment