Waldorf Rocket

[Paul Maddox]

Peter,

> Well, we're at that stage at work right now, QA testing the stuff I wrote a
> year ago. So I can see where they're coming from, let's do it quick and
> everything. Fine. But at least, keep supporting your products, and don't
> come up with a new one (again full of bugs) because that means you stop
> fixing bugs in existing products. And with that, they threw away their
> greatest asset: their customers.

The problem is, bug fixes cost time and money and don't bring an
immediate return.
If you have a "bean counter" at the head of the company (I have no
idea who is running waldorf these days) then that could be the
problem.
Also, IIRC, the old Waldorf went bust, so they may not own the IPR any
longer and may not have access to the code to be able to fix it.

I'm defending them, just offering alternative view points.

> I used to get updates for my Nokia E72 over two years after the thing came
> to market, and I was probably the only person in the world still using one.
> Apple gets out updates for their older models as well. Microsoft keeps
> supporting their products for 5 to 10 years. And technology moves a whole
> lot quicker in that area than with synths.

ACTUALLY, Apple don't, not for long anyway.
my old laptop run 10.5, no updates, Chrome have dropped support for it
and firefox won't update unless I update the OS.

> For me personally, it also puts a lot of doubt in their development team.
> It's not _that_ difficult to employ techniques and methodologies that try to
> minimise the amount of bugs you produce.

I think the problem is might be that they're trying to please 1000s of
people, by adding features that are handy, but probably won't get used
that often. There's nothing wrong with pushing your skills, but don't
aim for the sun when you can only reach the moon :)

> Wait, see, keep fingers crossed. :-)

I shall indeed.

Paul