3 ms·
Handling this gracefully would mean the developer can make that decision, explicitly. Ideally, the last piece of code I was working on would: 1. Detect GPU acc
by murgindrag 6y ago
Handling this gracefully would mean the developer can make that decision, explicitly. Ideally, the last piece of code I was working on would:
1. Detect GPU acceleration
2. With acceleration, enable fancy bells-and-whistles, with animations and effects
3. Without acceleration, fall back to good-old-fashioned mode, with flat HTML
A lot of this depends on what YOUR software does. Is it speeding up a spreadsheet (which will probably work fine in CPU)? Is it adding fancier shaders to a video game?
Explicit beats implicit. The library should support CPU and GPU, without a doubt, but the user of the library should make the decision of what to do if GPU isn't found.
- admax88q 6y agoThat's fair assuming that developers put in the effort to write the less fancy version. But if they don't I'd prefer to still have the option to run the software as written with worse performance.
- murgindrag 6y agoNo one's talking about taking that option away. All I'm saying is it should be an explicit option. When you initialize the library, you can pass a parameter. Or set a feature flag. Or whatnot. If you're writing a spreadsheet, use a fallback to CPU. If you're writing a glitzy animation, turn it off.