3 ms·
Do we know yet what the evolution and conditional-support mechanism is going to look like? Will there be "feature levels" like D3D, or ad-hoc independent extens
by mrec 5y ago
Do we know yet what the evolution and conditional-support mechanism is going to look like? Will there be "feature levels" like D3D, or ad-hoc independent extensions like interim GL, or some mix of the two?
Now that basically all relevant browsers are evergreen (sit down, IE11) I wonder whether an API roadmap could take advantage of that in a way that's less pesky than the traditional approaches.
- raphlinus 5y agoYou'll probably be interested in section 3.6 of the spec[1], "optional capabilities." One such is timestamp queries, which I find especially annoying when they're not available. [1]: https://gpuweb.github.io/gpuweb/#optional-capabilities https://gpuweb.github.io/gpuweb/#optional-capabilities
- pjmlp 5y agoIt will be extension spaghetti as always. Note that not even with the same browser version there are any guarantees regarding GPGPU support. A big difference between browsers and native 3D APIs is the blacklisting of client hardware/drivers, so one never knows what is actually being accelerated.
- enos_feedler 5y agoCould you explain blacklisting? What does this mean? Couldn't there be an API to probe whatever information the developer needs to determine acceleration?
- eptcyka 5y agoBrowsers blacklist driver/hardware combinations when they are known to be buggy.