mustang VS keyboard-configurator

It would be great for Rust to have a Linux target that doesn't use libc, but from what I've read, not many people are interested in this.

Found this as well: https://github.com/sunfishcode/mustang

Some discussion here: https://github.com/bytecodealliance/rustix/issues/76

On Linux there has been some attempts to get exactly this solutions, most notibly https://github.com/sunfishcode/mustang but the topic did not seem to fetch a prominent position on the supported feature list.

For Linux, Mustang already exists because Linux has a stable syscall API

Why bother with a libc at all, when you can skip it entirely on Linux!

Mustang is a project which is able to run some non-trivial programs written in Rust, such as ripgrep, without using any libc, on Linux.

Mustang is one way to take care of the tiny amount of "C" that runs before main().

This is more a Rust question than a Zig question. In Rust, the choice of a specific libc (or to not use a libc) is part of the "target", for example many hardware platforms have gnu/musl/none targets. See also relibc or mustang for pure-rust alternatives. Each libc alternative require some work to integrate into Rust.

There's a separate project for that, called Mustang. It's built on top of rustix and provides all those things. It's not super mature yet, but it is able to run ripgrep by itself: https://github.com/sunfishcode/mustang

Many or most of their keyboards are configurable these days. See https://github.com/pop-os/keyboard-configurator

Reported at https://github.com/pop-os/keyboard-configurator/issues/195 - I get a failure from dfu-programmer trying to update using the alternate update method with the keyboard-configurator app (because fwupdmgr won't update it because of the firmware bug that the new firmware addresses).

I found the ticket regarding Fn lock https://github.com/pop-os/keyboard-configurator/issues/159

keyboard-configurator

Good. I bought Darter Pro recently and had to - business as usual under Linux - compile this and tweak that. Via things like their keyboard configurator[1] I was exposed me to Rust's GTK bindings. It wasn't pretty: the mismatch between the obviously object-oriented GTK and Rust which doesn't do (and doesn't want to) OOP was glaring. I understand the appeal of Rust very well, and I'm happy they write their drivers and (parts of) firmware in it, but it's about as fit for OOP-based GUI as Go and Erlang. Which is to say - not very much.

[1] https://github.com/pop-os/keyboard-configurator

That's exactly what it's meant for, but the frontend of the configurator app doesn't seem to list those characters. You may consider opening an issue and relating to this one: https://github.com/pop-os/keyboard-configurator/issues/105

Probably a good issue to open here: https://github.com/pop-os/keyboard-configurator