Founder & CEO @Tracel_AI Building Burn, an open-source Deep Learning Framework in Rust 🦀

Québec, Canada
Joined January 2012
I think you just have to consider that some people like to have control, and that control has value with a big price tag on it.
Developers will be like, "I don't like paying $1 per build, I'll just buy this $15,000 mac studio so all my builds are free" not an accounting class in sight
1
5
390
Rockets are now a safety feature
The Roadster could genuinely be a lifesaver in situations like these.
104
Not true anymore, not since RL post training. Models are trained to maximize rewards, which can be anything
Ben Affleck says AI is simply matrix multiplication, linear algebra and floating point calculations, and however convincingly it sounds like a person, it has nothing to do with thought, humanity or feeling “Nor do I believe, and I think it’s important to draw the distinction between what AI does, which is simply predict the next token or the next word in a sentence, then add that word on, run it back to the machine, do a lot of computation and pick the next word." "That is a very different thing than sentience or thought. And I think we need to be really clear about that because it can be convincingly, in an illusory way, sound like thought or like a person." "But let’s be real clear. This is matrix multiplication. This is linear algebra. These are floating point calculations. It has nothing to do with thought, humanity, or feeling.”
1
180
Btw batch decode is compute bound, and keeping the KV cache on the same compute unit is valuable. The benefit of a different chip for decode is only latency, but it comes with a higher per token cost.
AI inference is shifting from single GPU clusters to Heterogeneous Disaggregated Inference. Prefill (compute-bound) and Decode (memory-bandwidth-bound) have completely opposite hardware needs. Instead of forcing H100s/B200s to do both (poorly), the industry is splitting the pipeline across specialized chips.
1
2
211
There will be two kind of AI products. The closed AI that is fully vertical, from the application layer to the chips. Then there will be open source AI that will provide more flexibility of choice to customers. They will be able to chose the software and hardware infrastructure, and the applications running on top.
Data brokers are now buying up SaaS data sets for anywhere from $100K to $2M SaaS are struggling now and some extra money to fill the gap by declining revenues is nice That data is then re-sold to AI training companies and AI frontier labs for the exact purpose of integrating whatever that SaaS did into the AI frontier lab's app Pretty obvious to see where this is going
3
104
Vim was about automating typing to reduce cognitive load and focus more on the problem. It was worth it and I'm happy I learned it as well
I still love vim and am so happy I learned it
1
1
6
238
C'est le docteur guéri tout qui a un remède à tout 🎶
POV: You told a rude Québécois kid who gave you grief for daring to speak English that fries are better with ketchup than as poutine, so now he's folk-dancing to defend the village's honour.
5
299
Commoditise your complement: if AI models are free, it's easier to sell the hardware to run them, and you get better margins
Nvidia’s bet is quite simple: If all AI tokens are generated by OpenAI and Anthropic, they will run on Trainium and Jalapeño, not Nvidia If open source models proliferate, and are designed to run cheaper on GPUs, Nvidia succeeds Open source is existential for Nvidia’s survival
4
359
The cube paradigm is quite beautiful and efficient
A team's code got a third smaller after moving from rust_cuda to CubeCL
4
270
Graph capture works on wgpu now, and Qwen3 0.6B decodes 25% faster with it on my Strix Halo. You capture one decode step once, and you just replay it.
1
1
2
243
WebGPU doesn't have a graph object like CUDA does, and you can't resubmit a command buffer. So we built a software graph. When you capture, we resolve the pipelines, the bindings and the bind groups once, and the replay just re-encodes the dispatches in a tight loop.
1
42
We just added compute environments to CubeCL, and it removes the JIT cold start. You load one, and it starts as fast as if it was AOT
1
1
2
8
1,449
The way it works is pretty simple. You run your workload once, but nothing actually executes, we just collect every kernel it's gonna need. Then we compile them all at once on every core, and autotune runs with everything already there. So when you load it, your model just runs.
2
54
And we'll support nvfp4 on all hardware, it's not going to be accelerated on non Nvidia GPUs, but it will work
cubek now runs nvfp4 on the tensor cores of an rtx pro 6000, ~1390 TFLOP/s. that's 3.5x f16 on the same path
6
318
True, I think we could support some NPUs through LLVM, but a lot of them just accept ONNX graphs, which is terrible
NPU was a miss. Limited programming model and a vendor specific API. Too much dev effort to support all different NPUs. Today everybody has a GPU with tensor cores. Apple M5/M6 has them, New Intel/AMD GPUs have them. Nvidia Turing (RTX 20) had them already 8 years ago.
3
109
Nathaniel Simard retweeted
Burn v0.22.0 is out > This release removes backend generics from models/tensors (device selects runtime), adds LoRA/QLoRA, multi-optimizers, graph capture, and faster rebuilds.
2
4
1
25
1,494
Burn 0.22 just shipped. The deep learning framework written in Rust got significantly faster to build, train, and deploy. 🦀 The headline change: backend generics are gone from user-facing code. Before: pub struct Model<B: Backend> { linear: Linear<B> } After: pub struct Model { linear: Linear } The backend is now selected through the device, not wired through every type. This breaks the compilation dependency chain that previously propagated through the entire application. Real measured rebuild times: → CNN project: 28.42s → 4.57s (6.2x faster) → Transformer project: 14.73s → 1.00s (14.7x faster) That's not a microbenchmark, those are real model-edit rebuilds on release builds. Training performance on CUDA also improved significantly: → CNN: 80% higher throughput, 49% less peak VRAM (956 MiB → 486 MiB) → Transformer: 3.6% faster, 18% less VRAM The VRAM reduction comes from adaptive memory pools that tune allocation sizes based on workload statistics, no manual configuration needed. What else is in 0.22: LoRA and QLoRA fine-tuning : attach low-rank adapters to frozen base weights, with per-parameter-group optimizer config. QLoRA keeps base weights quantized to reduce storage. ONNX export : export a Burn model to ONNX with one call. Early stage, limited operator coverage, but the direction is there. Remote compute via Iroh : run inference and training on another machine's GPU. Peer-to-peer, encrypted, authenticated. Repeated graph sequences are sent once and replayed by ID. CubeCL Environment : ship pre-warmed compilation and autotuning caches with your application. Works across native, WASM, and no_std targets. Graph capture and replay on CUDA and HIP : reuse kernel launch sequences without repeating launch preparation. NDArray and LibTorch backends are deprecated. Candle is removed. Requires Rust 1.95+. The team also hints at a native AI engine (LLM inference server + chat app + OpenAI-compatible API, all in Rust) shipping soon on top of Burn. Worth watching. 🔗 tracel.ai/blog/release-0.22.… #RustLang #MachineLearning #DeepLearning #OpenSource #GPU
4
7
31
1,223
And CubeCL is the best way to rewrite kernels in Rust 🦀
If it can be written in Rust then it will be written in Rust 🦀
2
4
17
530
Building on AMD made our CUDA side more reliable. I'd use nothing else than CubeCL to program AMD GPUs today.
1
3
10
530
The AMD runtime doesn't tolerate any error, and CUDA is way more forgiving. So AMD forces you to get the software right, and CUDA gets the benefit too.
2
67