On 2013-10-10 12:28 PM, Steve Fink wrote: > It seems like the optimal efficiency vs surface exposure vs frequency > of use tradeoff would be to do everything but the top formats (JPG, > PNG, GIF?) in JS.
That's what we do today. We support those three image formats with native code, and others can be supported by a js implementation, which anyone can write. Unless you mean we should maintain a js library supporting other formats? > Then for the top three, try to do a hybrid implementation where all > of the core bit-slinging is done with C/SIMD/GPU/quantum entangled > cesium ions, but all of metadata and other bits are done in JS. That sounds awkward to me. You're right that we have to be very careful with native parsers, and we are, but formats popular enough to adopt into the platform generally have widely-tested native implementations. Some things, like scaling and colourspace conversion can already be done with WebGL though, so the platform is making progress in this direction, which is helpful for minority formats. -r _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
