Re:Universal rendering with SwiftShader, now open source
by vegabook on Wednesday June 29, 2016 @02:45PM
(#12003698)
gees, even my $9 C.H.I.P supports OpenGL (ES). Talk about historyware.
[ Parent
| on HN ]
Re:Universal rendering with SwiftShader, now open source
by erjiang on Wednesday June 29, 2016 @02:52PM
(#12003762)
Chrome maintains a GPU blacklist of drivers and GPUs that it will not run WebGL on. According to [0], even hybrid Nvidia/Intel setups are excluded. So I wouldn't be surprised if there are many people with GPUs that "support" OpenGL ES but are buggy enough to be blacklisted.
[0] https://www.khronos.org/webgl/wiki/BlacklistsAndWhitelists
Re:Universal rendering with SwiftShader, now open source
by vegabook on Wednesday June 29, 2016 @02:56PM
(#12003792)
Okay so you're targeting a userbase of clueless boomers who can't be bothered to upgrade or go into chrome://flags or about:config. Fine. It's time to move on. Encouraging the continued use of a stone age endpoint is regressive. Fixing this is a single search away and can be pointed out easily to said users on a landing page. We have to start using the parallel silicon present in all our devices. It even makes sense ecologically.
Re:Universal rendering with SwiftShader, now open source
by magicalist on Wednesday June 29, 2016 @03:14PM
(#12003953)
> Okay so you're targeting a userbase of clueless boomers who can't be bothered to upgrade or go into chrome://flags or about:config
The blacklisting is often for security reasons. I would strongly advise against browsing arbitrary websites with the blacklist overridden.
Re:Universal rendering with SwiftShader, now open source
by pcwalton on Wednesday June 29, 2016 @02:51PM
(#12003758)
You'd be amazed how many browser users have broken unusable drivers, especially on Windows XP. Even if newer drivers are available, trying to instruct those users how to upgrade is a nonstarter. It's sad, but that's the world we live in.