sorry, I agree with @CCMP
there are many technical/project management reasons why maintaining/upgrading older ‘legacy’ software is harder… than releasing new shiny things which doesn’t need to care about past compatibility (or users sensibilities to a particular workflow etC)
it’s not ALL about money… of course, dev requires certain investment (in resources = money), nothing wrong with that (programmers need to eat ) , but there are also many structural issues, and also decisions about direction…when to make radical rewrites etc.
have Akai got the right ‘balance’ of investment … no one here knows, you’d have to be on the dev team, to know if they are lacking resources… or just struggling with an ageing code base, or original devs moving on to new things.
frankly, look at any (software/hardware) product thats been around a while, they all go thru peaks n’ troughs in stability…
Microsoft Windows/Apple macOS/ most gaming franchises… even Elektron call it a day on products after a while (e.g. octatrack)
for sure, consumerism does make all product have shorter lifespans… and that means companies cannot invest for quite so long in them (support costs, recouping r&d costs) , but thats also a function of technology advancement - tech is moving much quicker.
so frankly, I dont buy the rose tinted - ‘it was better in my day’ … less consumerism blah blah.
Im old enough to know that was not the case…
Do I agree with Benn’s underlying, "we should not be beta testers’
yeah, to some extent, though its also kind of inevitable given the short lifecycles.
BUT, I do think companies are using far too many non professional testers for QA.
sending a product early to YouTubers/Musicians is not how proper testing is done, and frankly some of the bugs Benn highlighted were the kind of thing you’d expect with this ‘casual testing’ approach, and the things Id expect pro QAs to pick up on.
Companies need to get back to having proper professional QA’s that know how to test, and only release once they sign it off.
is Akai doing this ? we dont know for sure, but it feels like their QA needs reviewing.
when a bug is released into the wild… not only should you ask - “how can we fix it?”, but almost as important is “How did we not notice this before release?”
(and guess what… this is also what I expect proper QA teams to do , but you wont get from ‘casuals’)