On 2013-10-10 12:56 PM, Brian Smith wrote:
On Thu, Oct 10, 2013 at 3:43 AM, Till Schneidereit
<t...@tillschneidereit.net> wrote:
On Thu, Oct 10, 2013 at 12:00 PM, Gabriele Svelto <gsve...@mozilla.com> wrote:
On 10/10/2013 02:36, Zack Weinberg wrote:
In that vein, I think we should take a hard look at the image decoders.
...
Considering the performance profile of some of our low-end platforms (most
Firefox OS devices, low-end Android devices too) I don't think that would be
a good idea right now.
...
Note that we'll have SIMD support in JS in the not-too-distant
future[1].
...
Things like this seem like really good ideas:
http://blogs.msdn.com/b/ie/archive/2013/09/12/using-hardware-to-decode-and-load-jpg-images-up-to-45-faster-in-internet-explorer-11.aspx
To whatever extent we can't match C or even hand-tuned assembly
performance for image decoding with JS (using whatever combination of
JIT, explicit SIMD coding, explicit GPU shader coding, etc. is
necessary), I kinda think that points at a gap in "the Web platform"
that we should fix - maybe not today, or tomorrow, but soon. We are,
after all, pushing JS as the One True Virtual Machine for everything;
anytime _we_ have to drop down to compiled language for something,
that's a place where someone else might also find that JS did not meet
their needs.
This argument applies equally to XSLT, forms, editor, etc. as being
discussed elsewhere, although I imagine the solutions would be different
in each case :)
zw
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
