tract VS gpu.js

Tract is the most well known ML crate in Rust, which I believe can compile to WASM - https://github.com/sonos/tract/. Burn may also be useful - https://github.com/burn-rs/burn.

tract!!

we use tract for inference, integrated into our runtime and services.

Not for training, but for inference this looks nice: https://github.com/sonos/tract

There's also tract, from sonos[0]. 100% rust.

I'm currently trying to use it to do speech recognition with a variant of the Conformer architecture (exported to ONNX).

The final goal is to do it in WASM client-side.

[0] https://github.com/sonos/tract

As the article notes, there isn't any official Rust-native support for any common frameworks.

tract (https://github.com/sonos/tract) seems like the most mature for ONNX (for which TF/PT export is good nowadays), and recently it successfully implemented BERT.

There are some DL libraries written in Rust: https://github.com/sonos/tract , https://docs.rs/neuronika/latest/neuronika/index.html . The second one could be used for training, I think.

You might already be familiar, but a GPU.js backend can provide some speedups via good old WebGL -- no need for WebGPU just yet!

[0]: https://github.com/gpujs/gpu.js/

Very cool project.

I learned WebGL three years ago but before I dove into the underlying concepts I used GPU.js [1] to quickly prototype my project. Eventually, the abstraction prevented necessary performance optimizations so I switched to vanilla GLSL and these vanilla GLSL "shaders" were initially ejected from GPU.js.

Writing JS code then looking at the generated WebGPU output is a great way to get familiar with WebGPU. Thanks for this.

[1] https://github.com/gpujs/gpu.js/

I used this library on my project but I think it's no longer maintained. I PRed a fix for buggy atan2 over a year ago and no movement [1]. I do highly recommend it if you're a web developer interested in harnessing parallel processing.

[1] https://github.com/gpujs/gpu.js/pull/683

Thanks for pointing this out. I've submitted a PR to resolve this: https://github.com/gpujs/gpu.js/issues/757

That being said, if you're not building from source (you're running an LTS version of node on a supported platform), you don't need to worry about python or many of the build deps.