Very good point, a company has to have cash flow. Also design efforts are expensive, and revenue needs to come in to fund that NRE. On top of that, some engineers really have little concept that the money has to come from somewhere, and you can't twiddle a design forever. Eventually you have to man up and sell the design.
OTOH I have seen quite a few sales folks that have little idea how engineering a product works, and in some cases go out of their way to be ignorant of the process, but will then assign an arbitrary date for completion that is forced on the engineers. And they get angry at the laughter that comes from the engineers when this is done.
In small companies, it's always a balance between resources\customer expectations\cash flow\and time. Often there are compromises that have to be made, and some of these criteria can be immobile.
All very true. Some people can absolutely have lofty or unreasonable expectations, which is why communicating about projects and ideas is an absolute necessity in business. Not being an engineer, I've had wrong ideas of how long a developments would take, but in talking with others can amend certain assumptions and expectations, and thus communicate them to dealers/customers/artists/etc.
Because I don't know the circumstances or inner workings at Kemper, I don't want to make too many assumptions. When it comes to the editor, it's something many others and I have said should have been there from day 1. In the 9 months since WNAMM, I can understand some rustling because that's quite a long time. Developers may go through scenarios in their head, but consumers start thinking about how other competitors have been able to accomplish similar software developments and upgrades in less time and with less hiccups. Or that's the way it would feel.
In any respect, it's been so long that I'm emotionally disinvested. When it's released I'll be pleased, but I'm not checking every day for it to disappoint myself.