Steve, just to provide some more clarification on my position... I think the main issue I have with ESRI's deprecation policy is that their sales and marketing approach is frequently out of sync with their development and training approach. There are many technologies that ESRI has advertised as THE technology for the future (Avenue, MapObjects, VBA, WebADF), even up to a very short time before they suddenly decide that these technologies are mature, legacy, or retired. In 1999, Avenue and MapObjects was heavily pushed as a primary customization platform, only to be eclipsed a year later by ArcGIS 8.0, ArcObjects, and VBA. Why wasn't their marketing team on the same page with their developers? This last year we saw the demise of VBA support in the Desktop platform, yet there are currently no training courses offered by ESRI that cover ArcObjects in the VB.NET platform (there is just one two-day course covering C# Add-ins). For those unfamiliar with ArcObjects customization, what is the recommended training path now that VBA is gone?
I feel that Esri has done very poorly with synchronizing their sales, marketing, development, and training strategies over the years, to the detriment of their end users. Two years ago Flex was the hot thing. When I began creating functional JavaScript API applications, our sales rep's first response was, "Why didn't you do it in Flex?". Now I am starting to see the tide shift a little toward the JavaScript API. I am glad to see that because I think it is more functional for my needs. I hope it continues to be supported for a long long time to come.
-Matthew