Please refer to my previous post, A Brief History in Time (DCTM Development), to get a perspective on the evolution of DCTM development.
With the birth of TaskSpace, the WDK/DFC development model was no longer an absolute necessity. Many clients as well as new developers have complained that it took too long to learn/customize WDK. I’m not saying that this is a bad thing (I am avid supporter of TaskSpace), but it did mark a change in the development paradigm. This was the start of the DCTM development divergence.
Based on the marketing materials for 6.5, it seems that EMC is addressing what the market is asking for and is focused on delivering solutions and not just technology (e.g. WDK). What clients and EMC executives may not have considered is that delivering these very specific solutions based on different technologies MAY increase the cost of customization. I’m not saying that the cost WILL increase, but as these various solutions use different technologies, it may be harder to find developers/consultants who can customize the individual solutions.
Today, if I need someone to customize Webtop, anyone with Web Publisher, DAM, or DCM can do this. This may not be the case tomorrow. A Flex developer might learn about DCTM by customizing Media Workspace. This person is not going to know how to customize Webtop or even CenterStage Pro (the full version of CenterStage Essentials that is supposed to have its own APIs). I know that the product managers for each of these products had their reasons for choosing these other development technologies for their products. EMC as a whole needs to focus its energy into developing the next WDK – a unified (not divergent) development paradigm.