Mathias 🦀
@mathiasb77.bsky.social
Interest in Rust, in particular for firmware development and embedded systems. Opinions are my own.
🇫🇷🇸🇪🇺🇸
🇫🇷🇸🇪🇺🇸
So much is happening in the world, you are going to have to be more specific 😀
July 27, 2025 at 7:38 PM
So much is happening in the world, you are going to have to be more specific 😀
You can use it in no-std projects (if relevant). The std part of the API is typically gated by a “std” feature enabled by default (and that is fine).
July 16, 2025 at 12:33 AM
You can use it in no-std projects (if relevant). The std part of the API is typically gated by a “std” feature enabled by default (and that is fine).
Nicely spotted! Not ideal, but depending on where and how small the test points are, that could work.
April 12, 2025 at 10:22 PM
Nicely spotted! Not ideal, but depending on where and how small the test points are, that could work.
The thing I am a little sad about is that there seem to be no SWD pins.
April 12, 2025 at 1:37 AM
The thing I am a little sad about is that there seem to be no SWD pins.
I agree that Cargo is a key part of Rust’s success, but not in isolation. The crates ecosystem would not be as good as it is without Rust’s type system, borrow checker, macro systems, etc. Code “composabilty” in C/C++ is not limited only by lack of standard build and package management system.
March 30, 2025 at 4:14 PM
I agree that Cargo is a key part of Rust’s success, but not in isolation. The crates ecosystem would not be as good as it is without Rust’s type system, borrow checker, macro systems, etc. Code “composabilty” in C/C++ is not limited only by lack of standard build and package management system.
I am wondering how long it’s going to take for someone to use AI to create some wild summary of the documents.
March 18, 2025 at 11:32 PM
I am wondering how long it’s going to take for someone to use AI to create some wild summary of the documents.
It happens twice a year. In our team, we nickname this a “time vortex”. The tools handle it in the way that makes most sense (anchored in the timezone of the organizer). Some recurring meetings that are normally adjacent will now overlap. Sometimes painful, or the opportunity to skip a few meetings.
March 9, 2025 at 3:54 PM
It happens twice a year. In our team, we nickname this a “time vortex”. The tools handle it in the way that makes most sense (anchored in the timezone of the organizer). Some recurring meetings that are normally adjacent will now overlap. Sometimes painful, or the opportunity to skip a few meetings.