conectado
tapingmemory.bsky.social
conectado
@tapingmemory.bsky.social
Unbothered. Moisturized. Happy. In My Lane. Focused. Flourishing. Working with Rust 🦀

My blog: https://taping-memory.dev
Reposted by conectado
Incredibly disappointed (shocked even) that the plan is to make the default Rust mutex not poisonable in the 2027 edition. Poisoning is one of the best examples of Rust focusing on rigor, and removing it from the default mutex would be a massive step backwards.
November 27, 2025 at 7:36 PM
Lots of people in the comments saying this was a C mistake. But C++ is not compatible with C, so it chose to inherit this problem.
"if you pass an array to a function it can no longer tell how big it is, you have to tell the function how big the array is in advance" - they made the language wrong then!

(i am joking but it is funny finding out how much harder this is than c# or python)
November 18, 2025 at 10:32 PM
Reposted by conectado
it's great that android moved to make rust capable of replacing c/++ in android (net new systems code is more rust now)

but eventually someone there's got to realize: rust could also be preferable to kotlin for the role it currently occupies
“We adopted #rustlang for its security and are seeing a 1000x reduction in memory safety vulnerability density ... with Rust changes having a 4x lower rollback rate and spending 25% less time in code review, the safer path is now also the faster one.”

security.googleblog.com/2025/11/rust...
Rust in Android: move fast and fix things
Posted by Jeff Vander Stoep, Android Last year, we wrote about why a memory safety strategy that focuses on vulnerability prevention in ...
security.googleblog.com
November 14, 2025 at 9:53 AM
Reposted by conectado
man, can you imagine a world where we poured 1, 10, or 252 BILLION dollars[1] into maintaining/developing open source, programming languages, dev tools, teaching material, documentation, etc?

like, god damn. 1/10 of that, and AI would probably work better too.

[1]: hai.stanford.edu/ai-index/202...
November 6, 2025 at 7:45 PM
Reposted by conectado
Rust programmers, do you worry about supply chain security? I.e., that a dependency might contain a bug or malicious code?
October 13, 2025 at 7:04 PM
Reposted by conectado
Happens every time....
October 7, 2025 at 4:21 PM
please, use mergiraf mergiraf.org I have been using it for the last few days and it's making my life so much easier.
Introduction - Mergiraf
A syntax-aware git merge driver for a growing collection of programming languages and file formats.
mergiraf.org
September 23, 2025 at 1:13 PM
Sometimes my hardware will simply stop working-- I think I'll need to buy proper debugging hardware tools.
September 4, 2025 at 12:21 AM
Reposted by conectado
Just a heads up to anyone using Firefox:
August 30, 2025 at 6:07 PM
I've no unsafe operation and memory is being corrupted 😭
August 27, 2025 at 9:32 PM
Is there a successor to FireDBG? github.com/SeaQL/FireDB...

The project looks absolutely awesome but development seems halted.
GitHub - SeaQL/FireDBG.for.Rust: 🔥 Time Travel Visual Debugger for Rust
🔥 Time Travel Visual Debugger for Rust. Contribute to SeaQL/FireDBG.for.Rust development by creating an account on GitHub.
github.com
August 27, 2025 at 4:49 PM
Did rust-analyzer started filling in variable names when filling matching arms? That's so great!
August 26, 2025 at 4:28 PM
New Benn Jordan video! (๑>ᴗ<๑)
August 26, 2025 at 3:31 PM
I've been thinking lately, that the distinction between local and distributed system is not that useful.

Every computing system is distributed at some scale, the distinctions are the characteristics of the I/O interfaces.
August 25, 2025 at 6:25 PM
Under the current definition of AI, a PID is AI.
August 25, 2025 at 6:22 PM
🙃 Are datasheets written confusingly on purpose?

"Hardware won't allow ERXWRPT to be updated to ERXRDPT" and "[Hardware] will always write up to, but not includ-
ing, the memory pointed to by [ERXRDPT]" are quite different.
August 25, 2025 at 2:27 AM
If I knew how to short companies I'd make so much money.
August 21, 2025 at 7:40 PM
It's an start! (it does work although the API is really unergonomic)
August 21, 2025 at 4:51 AM
My kingdom for a bytes crate that doesn't require alloc
August 21, 2025 at 12:01 AM
I hate password requirements so much.
August 20, 2025 at 6:48 PM
Is there a enumflags #rustlang crate-like but for operation between 2 different enums?
August 19, 2025 at 11:10 PM
Does someone have an example of sans-IO without alloc? It can be in #rustlang #C++ or whatever, I want some inspiration for my own crate.
August 19, 2025 at 4:11 PM
Reposted by conectado
I'm writing a #rustlang crate, I want opinions on what to use to represent non-byte aligned addresses. Right now I'm dealing with 5 bit addresses.
August 17, 2025 at 9:25 PM