syl20bnr

It will make more sense once you start using CubeCL. There's now a CubeCL book available: https://burn.dev/books/cubecl/.

It does come with some mental overhead, but let’s be honest, there’s no objectively “good” choice here without introducing bias toward a specific vendor API.

Learning the core concepts takes effort, but if CubeCL is useful for your work, it’s definitely worth it.

Burn is a new and innovative Deep Learning Framework in Rust and there is very few presentation material available about it. As an invited speaker at the 2025 "Scientific Computing in Rust" conference, Nathaniel made a first talk about why Rust was the best choice to make Burn and later CubeCL happen.

You are right we just released Burn and updated its readme, we were not thinking that CubeCL would be the one that could be featured. ^_^

I am the coder of the MSL dialect for the CubeCL CPP compiler. Since 0.5 release it directly compiles to MSL and support simdgroup matrix functions for instance. It does use wgpu for the runtime but without naga as we added msl pass through to wgpu just for this.

It also compiles directly to MSL, it is just missing from the post title.

More info on this here: https://github.com/syl20bnr/spacemacs/blob/master/doc/FAQ.or...

Can found more explanations on reddit for the bravest :-)

There is such support in Spacemacs, it is called "spacemacs layouts" but the tab is visible only on demand while pressing `SPC l`. Eyebrowse is also integrated in Spacemacs layouts so you can have multiple sub-layouts for a given layouts. Note that Spacemacs layouts also achieve buffer isolation so you can have a layout restricted to project's buffers only, you can also create your own rules to automatically add buffers to some layouts (called custom layouts). Last you can persist Spacemacs layouts across sessions.

And there is the `finance` layer for it with support for ledger :-)

Quick reply to address your issues:

- the binding menu idle time is configurable with the variable `dotspacemacs-which-key-delay`, check the docstring.

- The key binding you missed (should be listed in the quick start guide) is `SPC h SPC` which is used to find various info like FAQ, layers, packages config, dotfile variables etc... try it for yourself: `SPC h SPC which-key` and choose `dotspacemacs-which-key-delay` then RET, you can now modify its default value of 0.4sec to 0.

- `SPC :` to access _all_ interactive commands of Emacs (`SPC SPC` in develop, shortcut configurable of course).

- to discover how to close a window just press `SPC` then look for `window` and so on, it takes 10 seconds to discover it ;-)

- If you were not familiar with Vim you can choose to opt for Emacs key bindings and `SPC` becomes `ALT-m`, everything else is the same. But you are familiar with Vim so I don't see what issue you want to raise.

Thank you for trying Spacemacs :-)

It is by default `M-m`.

There is a Go layer: http://spacemacs.org/layers/+lang/go/README.html

You can launch an evil-tutor to start with Vim key bindings by pressing `SPC h T`.

Pressing `SPC (or M-m) t E e` will switch the editing style to Emacs (cursor becomes blue) and you should be at home :-) From there the Spacemacs key bindings are available behind `M-m`.

> * Configurable switch between modal/non-modal use of the command key.

This one is also provided in Spacemacs which is called editing style (vim, emacs or hybrid). It is possible to switch between them dynamically.

Auto-promotion here :-D Check Spacemacs, it is an Emacs configuration usable by Vim users out of the box. It has the feature you mentioned powered by the which-key package.