Hello Chris Wylie,
Let me start off with our full acknowledgment of the problem at hand. At telerik we highly value honest and direct communication with our customers. As the person responsible for the decision to reuse the namespace I will try to explain our reasoning behind it.
An year ago we started a massive campaign of migrating our ASP.NET controls from separate controls to the unified Telerik.Web.UI suite. This move created many challenges for us the main one of course being the work our customers will have to perform in order to migrate their applications. As a measure to reduce the changes needed to migrate the classic RadChart control to Telerik.Web.UI we decided to keep the namespace. Choosing another option would have meant an insurmountable amount of code to be fixed - something we cannot afford to ask our customers to do. We were aware that this decision had its drawbacks which you have elaborated here. Still we had to choose the lesser evil and pick a decision and stick with it.
Not a lot of our customers need to run the classic chart and the new one side-by-side. Actually for a whole year since we introduced RadChart in Telerik.Web.UI you are the first one to complain about this problem. Still we appreciate where you are coming from and what you have to say about our products. I can assure you that as a leading component vendor we take backwards compatibility very seriously and always do everything possible to minimize the impact major upgrades have on our user base. Unfortunately, as seen here, this is not always possible. Please, accept my sincere apologies.
the Telerik team
Check out Telerik Trainer
, the state of the art learning tool for Telerik products.