Microsoft Visual Basic and Visual FoxPro developers are still wincing over Microsoft's abandonment of their favorite platforms.
They had to throw out 100 percent of your code when .Net was introduced, and rewrite their apps from scratch, or just give up and call it a career. Now rumor has it that history is about to repeat itself.
.Net developers are getting nervous that they might end up in the same boat as their Visual Basic and FoxPro cousins. They were stunned at the absence of any .Net mention at the Windows 8 demo at D9. How do you introduce a new OS version and user interface paradigm without also showing developers how they will be building for it?
You could even argue that Microsoft is leap-frogging Apple. The Mac OS will be mired in the old user interface paradigm, requiring C++ and native API calls to get anything done, while Microsoft is embracing the technology that's driving the Web, cloud, Software as a Service, and mobile.
But what does that mean for MS .Net developers and their users? In Microsoft's usual style, they're following the trends, embracing with a bear hug late in the game, and re-inventing the wheel. In the process, collateral damage is acceptable -- even if it's their loyal developer base that gets sacrificed. Microsoft still believes that rip and replace is superior to fluid evolution of platforms. Out with the old, in with the new, and to hell with your millions of lines of proven code.