You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Access to tensor-accelerators such as GPUs or TPUs is fragmented and lacking cross browser support.
Running machine learning models, I am using WebGPU on Chrome Canary, WebGL on Chrome stable, WebGL on Safari's main thread, but not Worker thread, where I have to use WASM, etc...
Rationale
Machine learning is the future of software development.
However, nowadays support is fragmented, and runtime is extremely slow.
It looks like this proposal overlaps with #161 for OffscreenCanvas and #185 for WebGPU. (Although note that WebGPU is a Investigation Effort proposal, since there are no tests.)
If WebNN is the missing piece, I would suggest filing a proposal for just that. What do you think?
Thank you for proposing Machine Learning in the Browser for inclusion in Interop 2023.
We wanted to let you know that this proposal was not selected to be part of Interop this year. We had many strong proposals, and could not accept them all. As mentioned in the issue comments, WebGPU and OffscreenCanvas were considered separately for Interop 2023.
For an overview of our process, see the proposal selection summary. Thank you again for contributing to Interop 2023!
Description
Access to tensor-accelerators such as GPUs or TPUs is fragmented and lacking cross browser support.
Running machine learning models, I am using WebGPU on Chrome Canary, WebGL on Chrome stable, WebGL on Safari's main thread, but not Worker thread, where I have to use WASM, etc...
Rationale
Machine learning is the future of software development.
However, nowadays support is fragmented, and runtime is extremely slow.
Specification
Tests
The text was updated successfully, but these errors were encountered: