denog
webnn
denog | webnn | |
---|---|---|
5 | 5 | |
39 | 315 | |
- | 1.6% | |
6.6 | 9.3 | |
about 1 year ago | 5 days ago | |
Rust | Bikeshed | |
MIT License | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
denog
-
Deno 1.39: The Return of WebGPU
> integrate a minimal native system glue library into Deno
have you tried denog? https://github.com/denogdev/denog
- A fork of Deno with built-in window system integration
- Denox: A JavaScript runtime for gamedev written in Rust.
- Denox: A fork of Deno with built-in window system integration.
- Screenshot Saturday #635 - Perfect Placement
webnn
- Py2wasm – A Python to WASM Compiler
-
Ask HN: What's the idea behind the WebNN API?
The WebNN API will make it possible to run AI models in the browser: https://www.w3.org/TR/webnn/
The idea of having AI in browsers (see the "Application Use Cases") seems cool, but on the other hand, the idea of downloading & storing large models for each website/webapp seems terrible.
It seems to me that it would make more sense to have models built into browsers, and to have a web API that provides standardized ways to interact with the underlying models of each browser. From what I have understood from the WebNN spec, though, despite listing out all of the cool use-cases, the API doesn't seem intended to provide higher level functionality than loading, running & performing operations on a model.
Is my understanding of the API right, or is there something else that uses it to make these use-cases available in browsers?
- Deno 1.39: The Return of WebGPU
- W3C Candidate Recommendation Draft: Web Neural Network API
- WebNN: Web Neural Network API