I am not sure that you really have a point here.

Personally, I would advise against using the Telerik controls, outside of the menu system.  I have much better results in numerous ways using jQuery-based solutions over component vendors.  However, there are many options outside of the telerik controls. No one is required to use them, develop with them, or anything else.  DNN Corp simply stuck a deal to be able to offer it up as one of many options open to module and skin developers.  For those of us who have been in the community for a long enough time, this has been talked about over and over for several years.  Even though I don't jump at the chance to use Telerik, I am a HUGE fan of their control suite, and I am happy to have it as another tool in my toolbox, should I choose to do so.  I just so happen to own a developer license.

The point I am trying to make here is this: Can you safely remove the Telerik dll's from the CE version and still be able to use the system? If it will work, then DotNetNuke CE is still open source and only limited by its open source license. In that case I stand corrected. If the system is broken after the components have been removed, I have a point. In that case DotNetNuke CE is limited by its open source license and whatever the corporation and Telerik agrees upon at the current time or what future IP holders choose to allow or disallow in the future. I see the real value of DotNetNuke as being open source. It provides safety and predictability. The 0 dollar or 2000 dollar pricetags I don't care about.

If you do not address the Telerik namespace directly you're safe. The framework will provide wrappers that are available to anyone.

On another note: I don't get the "they're taking it away from us" regarding Telerik. Telerik was added and so are the wrappers. You still can (and I do) use your own controls. Nothing's stopping you.

Peter