Quote:
Originally Posted by steveh
With Haxe / OpenFL it's possible to bring in a lot of other libraries that will eat up physical memory but might only actually be used for one small function within an app. I assume that was Spiderplant's point about stripping out unnecessary stuff. Developers using Haxe are also mostly targeting mobile or desktop devices with much larger physical memory than the TiVo so there is less incentive for them to ensure an efficient memory footprint. Adobe Air in comparison was built to support lower-end devices.
Someone I know who evaluated Haxe for a project also said that it was not especially clean when it came to memory leaks and in a device like the TiVo where an application is running for a long time that is more of an issue than in a mobile phone app. You would expect these things to improve in time - this was a first release - though I get the impression the TiVo dev team is not especially large and time spent firefighting issues like this after a major architectural change mean less time on new features or improving the UI.
|
This is pretty much what I've heard in and around the industry. For the record though Adobe Air was first touted as a platform on which to build Flex apps as desktop apps as opposed to browser based apps. But I think once that wasn't taken up it moved more into the mobile market. Also Air doesn't protect lazy/less experienced developers from pulling in rafts of dependencies and Haxe is the same. Developers need the experience working with it and the discipline to protect their target device.
We could of course be totally wrong but My initial thought on reading Spiderplant's "paging" comment was memory leak or bloated software (didn't think it would be from the apps though).