I work with Adobe Experience Manager (former Day CQ) and the way the content is managed is the best, I have experience with. Of course, it does not mean, the product is perfect. But the concept feels right.
I really, really hope they succeed, but they've bitten off a difficult problem. It's not hard to design a simple content management API. What's hard is making it general enough to handle many situations without getting too complex.
We've been around for more than 3 years now, have clients with hundreds of published sites and we're profitable, so we're not going anywhere.
That said, the lock-in is a problem and I wish there was a really great way to address the lock-in. Open-sourcing doesn't really solve it when the software is built to scale up to handle thousands of multi-tenant sites on a distributed infrastructure, but not to be simple enough to install and run that it's viable for a relatively small number websites.
The largest obstacle for me to adopt such a system is that it requires me to bet my company's content on your system being around. I've looked at, for example, Webpop which is different but has some similar ideas - but I can't get away from the fact that Webpop may or may not be around in a year, so betting on it isn't something I would want to do.
That's what continues to push me to Wordpress and the like, although recently I've been spending more time with static web generators like Harp and DocPad. Those have a similar issue - my boss saying to me "Well, I know we can find Wordpress developers, but will wevbe able to find a Harp developer?"