Nat Friedman writes a nice post about two development approaches: Getting nothing wrong versus getting it right. Though I know nothing about Muine, I can see the analogy with the software I developped (or at least what I try to achieve). While some competing products don't attack the ease of use and simply stick with a "most common features" list, I've always felt it was important to improve interface too. And that applies to class libraries as well. The Xceed Zip for .NET object-oriented design may require some getting used to, but you end up with obvious and short code. In fact, it's more "forgetting about the old interface" than "learning the new one".

Another good example is Money and Quicken: While they both fight to have all the features the other one has, the resulting applications are not addressing my needs. My wife and I split general expenses based on our salaries, and house expenses half and half. I'm stuck with Excel for managing all this. The personal finance software world needs a Muine of its own... I'm ready to live with its "wrongs"! Suggestions?