If the KDE project openly acknowledged the previous attempts in this field that fell short of their intentions, analyzed why those projects did not achieve what they intended, and explained how they will avoid those pitfalls then, speaking for myself, I'd be more optimistic about their chances of success.
When they don't even appear to notice those previous problems it creates the impression that they'll end up in the same place as those other projects.
Posted Oct 17, 2012 13:46 UTC (Wed) by dgm (subscriber, #49227)
[Link]
Unfortunately this is very common. And I say unfortunately because in software development, like in science, negative results are as important as positive ones. It's my impression that projects that openly admit and discuss where they suck are the ones that get fixed sooner.