[elvin_d]

I’m glad not completely off with my bet 5 years ago that Rust will get larger chunk of the market. With the spread of AI Rust feels like a good candidate among Typescript and Python giants in a an era of coding assistant tools that needs a good nudge like Rust compiler.

[Zee2]

As a counterpoint, Rust is one of the languages that AI is worst at writing - currently, at least.

Perhaps there could be a future where the compiler/checker will be able to integrate more closely with whichever agent is attempting to write Rust - more closely than the current paradigm, where a hapless Claude repeatedly bashes its head into the borrow checker to no avail.

[redman25]

I think I disagree with this sentiment. I’ve found AI to be poor at one-shotting rust but give it a short agentic loop running `cargo check` and it can often produce code more solid than that created with a dynamically typed language.

[thekingofravens]

And when it does finally make something that works in Rust, its admittedly far more trustworthy than AI code in other languages. It does struggle a lot though.

[akkad33]

> Rust is one of the languages that AI is worst at writing - currently, at least

Everyone makes similar statements about AI, Ai is currently bad at this or that. I find it quite good to write Rust. Can you give a concrete example of what AI failed to write for you

[josevalerio]

Not OP but it consistently says that logging JSON (specifically nested JSON while not having escaped strings) with the tracing crate is not possible or provides wrong solutions.

However this is doable, just under an experimental feature flag since 2022[1]. I created this repo[2] with a small blog post, hopefully the scrapers can pick it up :')

[1]https://github.com/tokio-rs/tracing/discussions/1906

[2]https://github.com/joswayski/tracing-valuable-example