News for hackers. Stuff that matters.
Re:Gpu.js – GPU Accelerated JavaScript by chrismorgan on Wednesday February 27, 2019 @08:28PM (#19268323)
Browsers do a lot of blacklisting of drivers with known problems.

Things are slowly improving, especially as browsers themselves, especially Firefox, steadily do more GPU stuff (putting pressure on the driver makers to fix things), but there’s a reason why it’s been very rare for non-game UIs to target GPUs for rendering: GPU drivers are atrocious. Even if they don’t crash, the number of absolutely fundamental and critical bugs that they have is very impressive. As an example of a fundamental thing being broken, try https://github.com/tomaka/winit/pull/332#issuecomment-341383... and later on down in the thread where a driver update fixed it.

Re:Gpu.js – GPU Accelerated JavaScript by frankchn on Thursday February 28, 2019 @01:23AM (#19269372)
As another example, here is the long list of blacklisted drivers and cards in Chrome: https://cs.chromium.org/chromium/src/gpu/config/software_ren...
Re:Gpu.js – GPU Accelerated JavaScript by 43920 on Thursday February 28, 2019 @12:35AM (#19269166)
The list of driver issues that Mozilla has run into while developing webrender is also impressively long: https://github.com/servo/webrender/wiki/Driver-issues
Re:Gpu.js – GPU Accelerated JavaScript by chrismorgan on Wednesday February 27, 2019 @11:42PM (#19268994)
(Actually, I misrecalled the cited example: the driver update fixed that bug, but introduced another far worse one.)