btleplug VS Rust-for-Linux

Compare btleplug vs Rust-for-Linux and see what are their differences.


Rust Cross-Platform Host-Side Bluetooth LE Access Library (by deviceplug)


Adding support for the Rust language to the Linux kernel. (by Rust-for-Linux)
Our great sponsors
  • InfluxDB - Access the most powerful time series database as a service
  • SonarLint - Clean code begins in your IDE with SonarLint
  • SaaSHub - Software Alternatives and Reviews
btleplug Rust-for-Linux
9 75
514 3,472
4.3% 2.2%
5.5 10.0
7 days ago 9 days ago
Rust C
GNU General Public License v3.0 or later GNU General Public License v3.0 or later
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.


Posts with mentions or reviews of btleplug. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-05-03.


Posts with mentions or reviews of Rust-for-Linux. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-05-01.
  • The Linux Kernel Module Programming Guide
    2 projects | | 1 May 2023
    Ctrl-F "rust" links to LWN articles at that suggest that only basic modules are yet possible with the rust support in Linux kernels 6.2 and 6.3.

    Rust-for-linux links to the Android binder module though:

    > Android Binder Driver: This project is an effort to rewrite Android's Binder kernel driver in Rust.

    > Motivation: Binder is one of the most security and performance critical components of Android. Android isolates apps from each other and the system by assigning each app a unique user ID (UID). This is called "application sandboxing", and is a fundamental tenet of the Android Platform Security Model.

    > The majority of inter-process communication (IPC) on Android goes through Binder. Thus, memory unsafety vulnerabilities are especially critical when they happen in the Binder driver

    ... "Rust in the Linux kernel" (2021) :

    > [...] We also need designs that allow code in the two languages to interact with each other: we're particularly interested in safe, zero-cost abstractions that allow Rust code to use kernel functionality written in C, and how to implement functionality in idiomatic Rust that can be called seamlessly from the C portions of the kernel.

    > Since Rust is a new language for the kernel, we also have the opportunity to enforce best practices in terms of documentation and uniformity. For example, we have specific machine-checked requirements around the usage of unsafe code: for every unsafe function, the developer must document the requirements that need to be satisfied by callers to ensure that its usage is safe; additionally, for every call to unsafe functions (or usage of unsafe constructs like dereferencing a raw pointer), the developer must document the justification for why it is safe to do so.

    > We'll now show how such a driver would be implemented in Rust, contrasting it with a C implementation. [...]

    This guide with unsafe rust that calls into the C, and then with next gen much safer rust right next to it would be a helpful resource too.

    What of the post-docker container support (with userspaces also written in go) should be cloned to rust first?

  • The state of Flatpak security: major Projects are the worst?
    3 projects | /r/flatpak | 20 Feb 2023
    Rust-for-Linux issue tracker
  • rust devs in a nutshell
    2 projects | /r/ProgrammerHumor | 14 Feb 2023
  • Rustproofing Linux (Part 1/4 Leaking Addresses)
    2 projects | /r/rust | 10 Feb 2023
    Also, there already exists both issue:
    2 projects | /r/rust | 10 Feb 2023
    Yes, I definitely agree that it's a problem that pr_info implicitly wraps its arguments in unsafe {}. I wrote my own Pull Request with a trival fix.
  • how to compile a rust "hello world" with kernel 6.1?
    2 projects | /r/rust | 23 Dec 2022
    Note that this template won't work with Linux 6.1, which has very minimal Rust support. You'll want the RustForLinux tree, or maybe Linux 6.2.
  • Rust in the 6.2 Kernel
    2 projects | | 18 Nov 2022
    > Also we’re bringing NPM style supply chain problems to the kernel now?

    Nope. They've thought that through.

    (In fact, cargo is only used to build test helpers.

  • Asahi Lina on her experience writing a driver in rust
    4 projects | /r/linux | 5 Oct 2022
    The alloc library is available if a global allocator is available. Rust for Linux implements a global allocator (or, more accurately, hooks into the kernel's existing allocator, in rust/kernel/, and therefore you can use the alloc library in the Linux kernel.
  • Rust for Linux officially merged
    7 projects | /r/programming | 4 Oct 2022
    Here's the tracking issue for unstable features used.
  • Initial Rust support is now merged into the Linux kernel!
    2 projects | /r/rust | 3 Oct 2022
    There’s a Github repo for the Rust support and the maintainers actually accept pull requests and issues there. They’re quite responsive too and you’ll get excellent feedback on your submissions.

What are some alternatives?

When comparing btleplug and Rust-for-Linux you can also consider the following projects:

buttplug-rs - Rust Implementation of the Buttplug Sex Toy Control Protocol

gccrs - GCC Front-End for Rust

jakt - The Jakt Programming Language

rustig - A tool to detect code paths leading to Rust's panic handler

rfcs - RFCs for changes to Rust

dafny - Dafny is a verification-aware programming language

PrawnOS - Libre Mainline Kernel and Debian for arm laptops

koka - Koka language compiler and interpreter

cxx - Safe interop between Rust and C++

no-panic - Attribute macro to require that the compiler prove a function can't ever panic


rustc_codegen_gcc - libgccjit AOT codegen for rustc