From what I've read, it looks like the people most concerned are the ones who have become accustomed to the 'visual' programming interface. I left corporate IT

From what I've read, it looks like the people most concerned are the ones who have become accustomed to the 'visual' programming interface. I left corporate IT over 8 years ago for my own biz (after over ten years of doing it nights and weekends) but I was an administrator and an MCSD/MCDBA who made unix and windows play nice together so I often was approached with broken enterprise apps that almost always turned out to be Access .mdbs or VB programs that were being used by hundreds of people across large networks for critical (often financial) tasks. Fixing them taught me a lot about the capabilities of the authors (hard working good people) who were allowed to appear as much better software developers than they actually were. Going through 'wizards' and setting properties in a drag and drop visual environment are great for prototyping but these developers were often pressured by their managers to make these prototypes live immediately. Problems were fixed with 'work arounds' and users complained constantly. Often, all I had time to do was clean it up, trim it down and move it to a SQL Server. A temporary fix at best. I can only imagine that the fear of losing support for these tools is driving a lot of the forum posts that I have seen. I for one am extremely curious to see what microsoft considers to be HTML5.