12-Mar-2015, 11:03
Going back to AIR and its problems, and a lot of guesswork on my part but hopefully relatively (!) informed guesswork. AIR appears to be built on the QT framework which provides multi-platform capability and a nice environment to develop software fairly rapidly. I'm taking a guess here and thinking that AIR has been based on that framework from conception. Now I don't feel that AIR is a fairly typical QT framework implementation. It has real-time requirements that are fairly uncommon in most apps. It is possibly more low-level in terms of hardware than most implentations. I'm taking a guess that Devialet have become a slave to the framework and its insufficiencies and this had led them up something of a blind alley regarding bug-fixing. I'm guessing they've found themselves in a situation where they can't fix problems because it's in the framework, and that's beyond their control unless they start hacking that framework, which is a dangerous route to start taking.
Linn had a similar problem with Kinsky. They based it on the Mono framework and led them to a situation where most of the issues were being caused by framework bugs or going beyond the capability of the framework. One of the steps they took with Kazoo was to dump Mono, and (I think) build from the ground up. The investment required in time and money to do this was not insignificant.
Now with Dialog at least they have a single piece of hardware on which to develop. From that perspective, with any luck it's going to be a lot easier for them to find quick resolutions, and not to have to rely on third parties to implement framework fixes. I don't know if the SPARK client frontends are a ground-up development or not though?
Linn had a similar problem with Kinsky. They based it on the Mono framework and led them to a situation where most of the issues were being caused by framework bugs or going beyond the capability of the framework. One of the steps they took with Kazoo was to dump Mono, and (I think) build from the ground up. The investment required in time and money to do this was not insignificant.
Now with Dialog at least they have a single piece of hardware on which to develop. From that perspective, with any luck it's going to be a lot easier for them to find quick resolutions, and not to have to rely on third parties to implement framework fixes. I don't know if the SPARK client frontends are a ground-up development or not though?
