To me it definitely seems like they’re saving features for the next platform, eg to milk as much money as possible during intermediary steps.
Story about limited space on chip I don’t buy. Wonders can be done in what, 32k? I forgot how much exactly, but whole non trivial game fit in some unimaginable little space.
If that really was the issue, refactoring to condense code could yield a lot of space. Seeing how many companies do their IT products, unfortunately I’m inclined to stereotype that many write ugly repeatable and not optimised code. I work in IT, my hubby and best friend as well. We’ve seen a lot of ugly code. I can’t recall if anyone ever mentioned they’ve seen some really short and effective code in production (for the code written before we came), but bloatware is all around. Yes, I comment other people’s code because that’s what you get when you start somewhere. Rarely you start from zero.
And of course, changing old code is never a priority, and management usually doesn’t improve optimisations. Because they’re blind that that would bring money on the long run (eg by clearing the space needed to implement new features).
Yes it’s stereotype about sw development, seen in small and big companies. Phonak isn’t even an IT company, so there’s even smaller chance that some developers can push the change up towards management, since most of them aren’t from developer backgrounds.
Yeah, I’m not hopeful
Sorry for the rant
If I’m wrong, then I’d very much like to apply for a job there