That led to comments like “writing on the wall”, “head in the sand” and conjecture on lack of sales vs. Regardless, we didn’t get an official statement from Microsoft, other than it was happening, and the Fox community was left to piece together the reasons. YAG may have been constrained in what he could/should say in his position, and I imagine there was some disagreement with the decision within the Fox Team, but those are just guesses. However, at the time, I wished Microsoft would have been more transparent and given a more thorough explanation of their reasons for making that decision. With that in mind, I think it’s good to look at Microsoft’s treatment of VFP and how their decision processes work in regard to development tools.Ĭan you believe it has been over four years since Microsoft posted A Message to the Community and announced that Microsoft would cease development on Visual FoxPro? It has been over three years since Microsoft released VFP9 SP2 and Sedna, and over six years since VFP 9.0 was released! While I was saddened that Microsoft chose to cancel VFP, I appreciated the sensitivity the Fox Team, particularly YAG, showed to the Fox community. Since then, Microsoft has put a lot of emphasis on HTML5 and introduced Windows 8 and the Metro UI, leaving a lot of existing MS developers wondering about the future of their previous technology choices. About six months ago, I wrote most of this article, then decided not to post it. For a while now, I have debated whether or not to post this entry.
0 kommentar(er)
