We'd done some profiling to try to reduce the start-up time for a big automotive HMI project that's running on AIR 3.4 on an embedded Linux device. We found that a full second was being lost in the registerPrograms function, so changed this to only register the programs that the software needed (which was just a colored Quad and a number of simple Image textures) which took the start-up down to 20ms.
We'd like to contribute this change if possible, our customer would prefer to use the formal Starling releases so it would be great if this could be taken on board. We're happy to help work on adapting this e.g. to make it configurable one way or the other perhaps in case that's necessary. We've not done full testing on this yet but are planning to, I wanted to raise this and see what people thought.
We tried a simple app on an Android handset and the start-up time was reduced by just over 1.5s on average, this again just used a Quad and an Image but I don't know how many people do actually need all 70+ programs!