News for hackers. Stuff that matters.

A comment on Replacing JavaScript Hot Path with WebAssembly. Parent comment

Re:Replacing JavaScript Hot Path with WebAssembly by bzbarsky on Thursday February 14, 2019 @10:53PM (#19168346)
The article mentions why they couldn't use canvas for this: they are running this code in a worker, and canvas support in workers is not great in browsers so far.
[ Parent | on HN ]
Re:Replacing JavaScript Hot Path with WebAssembly by jaffathecake on Friday February 15, 2019 @03:28AM (#19169367)
Not only that, there's a nasty bug in Chrome that makes it unusable for our use-case https://bugs.chromium.org/p/chromium/issues/detail?id=906619
[ Parent | on HN ]
Re:Replacing JavaScript Hot Path with WebAssembly by olliej on Thursday February 14, 2019 @11:00PM (#19168366)
Ah my bad for skimming - I though most canvas stuff worked these days? (I recall many years ago when I worked on such things that fonts were the biggest problem, but also people generally wanting to be able to paint dom elements in their as well)
[ Parent | on HN ]
Re:Replacing JavaScript Hot Path with WebAssembly by Technetium_Hat on Saturday February 16, 2019 @01:03PM (#19179898)
It is OffScreenCanvas, the variant that works in web workers, that has poor browser support.
[ Parent | on HN ]