Fair! I've tried to keep the 'I' out of it in my version. Sounds more professional/serious.

Also, typo: Do no accept -> Do not accept

Lies! This is true in the Netherlands as well for most theaters

I think this blog post comes closest to my current thinking on AI than any other I've read: fransskarman.com/im_not_using...

I'm *very* excited to report that we got initial funding and have hired our first Rust maintainers!

RustNL's Rust Maintainers Team starts out with two full time maintainers, one intern, and five part-time maintainers, now stably employed to continue their work on Rust! 🎉

rustnl.org/maintainers/

Middels mijn airco's zit ik nu op minder dan 200m3 gas per jaar waardoor de vaste kosten hoger zijn dan de kosten van het gas zelf. Per m3 gas betaal ik dus nog bijna €1,50 extra aan vaste kosten. Ik wil dus ook naar all-electric. Als de vaste kosten naar 0 gingen voor me, dan had ik minder haast

Rust should have stable tail calls - Trifecta Tech Foundation Tail calls in Rust have been talked about for a long time, but especially from the outside it looks like very little progress has been made. Let's change that!

Folkert and Waffle have submitted a project goal to move explicit tail calls forward in 2026. In this blog, Folkert explains the work ahead: trifectatech.org/blog/tail-ca...

@wffl.ihatereality.space

#rustlang

Is your async too fat? You can trim it down with these tips!

Please share as I've noticed not many people are aware of this. This is also just part 1 of a 2 part series. Part 2 should be out soon!

Great news coming from Hungary btw 😁

Good to have you back!

Showing the extra '/' in the RA output

Showing rustdoc rendering it without the slash (correctly)

Output of RA macro expansion has the extra slash too

Anybody know why rust-analyzer is showing me an extra '/' in the inline doc view?

This happens when I generate code using the doc attr and with '///'.

Rustdoc is rendering it fine, so... RA bug?

Just wanna make sure I'm not missing anything before I open an issue :)

Looked it up. Rust 1.78 stabilized it 1 year & 11 months ago

At best new-ish 😋

It been there a while, but I've not seen it used much.

doc.rust-lang.org/reference/at...

There are two lints like this. The other one is newer iirc

Oh that's a pretty cool feature!

Crazy how much they've been able to pack into a single brick

Bringing Rust to the Pixel Baseband Posted by Jiacheng Lu, Software Engineer, Google Pixel Team Google is continuously advancing the security of Pixel devices. We have been f...

2 years ago I did a PoC to run #rust 🦀 in the #pixel modem

Today it shipped in millions of devices!

They grow up to fast! 🥲

security.googleblog.com/2026/04/brin...

#rust #security #smartphone #baseband

Any idea what those copper wires are for?

```rust #[diagnostic::on_unimplemented( message = "no `register-address-mode` is specified in the driver, so multi-register operations are not possible", label = "not supported for this driver", note = "if you are the author of the driver, specify `register-address-mode` in the device config to enable this feature if the device supports it", note = "not all devices support this feature" )] #[doc(hidden)] pub trait AddressMode { #[doc(hidden)] fn next_address<A: Address>(current_address: A, current_size: usize) -> A; } ```

The previous code, but now applied to a Rust error message. It uses the provided text and changes the default error

Cool! I can now tell people about DDSL features through Rust error messages. This is pretty neat :)

#rustlang

Welp, I got laid off. RIP futurewei OSS rust team.

If you know anyone hiring systems engineers lmk.

Dented radar module, paint damage and a broken grille on the front of a car

Always nice to start the weekend on a positive note. Not this weekend though.

Seems like someone's hitch didn't like my car

Ooo

github.com/zpg6/embassy...

Oh, this is in the Go ecosystem. I thought maybe toml-rs went full claude 😅

Cool, good luck!

Yeah, it's why I explicitly mention stackoverflow. There's a lot of overlap in concerns. Largely it's been fine.

There's a bunch of ethical questions about AI, but IMO those are personal considerations everyone needs to make.

But I've got great copyright concerns that I can't allow in my repos

Yep! It pretty much reflects my own usage (though I have not yet asked an agent to explain a codebase to me or to debug it for me)

Some people have asked if they could copy the text. And yes!

I've marked the file as CC0 to explicitly allow you to.

Haha, well steal away!

That reminds me I should probably add a license for all non-code stuff in the repo...

Anyways, I've been thinking about AI use in my projects and I've written a guideline for it that severely limits what you're allowed to do with them when interacting with the project.

github.com/diondokter/d...

I might copy this to some more repos.

Maybe!

But with Rust I throw away the target folder willy nilly. I don't think you could do the equivalent in the setups you're describing.

So yeah, all I wanted to say is that LLMs are not simply continuing the trend. They're different altogether.

If someone only committed assembly to their project that was generated using a compiler without the associated source, I'd have low confidence in their work.

Imagine writing some C code, running the compiler to get the assembly, only to then commit the assembly to git *and trow away the C code*.

Nobody does that with code! And yet for LLMs that's normal practice. It would be untenable.

That may seem logical. An LLM can be seen as a natural language compiler.

But there's a big difference in the relation between the source and the artifact. The way LLMs are used, is very different than we do with code.

So, a major through-line of computer science over the decades has been the ever increasing abstraction level.

We (generally) don't worry about individual bits and clocks anymore like in the early days.

It's been said that LLMs are simply the next step in this evolution.