Rust's error messages are still unrivaled.

filtra.io | Breaking The AI Infra Monopoly With Rust- Tracel AI A filtra.io interview featuring Tracel AI.

filtra.io/rust/intervi...

CUDA, CUDA, CUDA... What if there was a different, open way to write highly-efficient GPU kernels?

This is the big swing that Tracel AI is taking. And, guess what... Rust is key to their approach. Check out our podcast with Tracel CEO Nathaniel Simard (linked below):

Explain that for me

Facetious answer or real answer lol?

What are things that software engineers think are really important that just aren't when you zoom out?

Is there such a thing as artisanal software? If so, what does it looks like? Examples?

Artisanal: products made by hand or using traditional, non-mechanized methods by a skilled craftsperson, typically in small batches

If LLMs are good at translating from one programming language to another (I think they are), then we should be seeing less programming language-specific requirements in software engineering job postings.

For those in the job hunt, does this match what you're seeing?

Seems like we need to figure out continual learning for the next step of AI...

The fact that SOTA is models built in Python is a big barrier to getting this done since Python is not highly cross-platform.

Does anyone know of a language that might be good for this...? 🦀😉

One last thought on this. Over time, I think you could make this even better by making specific skills or maybe sub-skills for specific Rust use cases like safety critical.

I also think something like this could further Rust adoption if it proved highly effective.

I should also note that I have been searching and seen some smaller, fragmented attempts at this.

There is so much tribal knowledge about writing Rust that I think could be brought together to dramatically improve agents.

One of the big advantages of Rust is that it is a language that DOES tend to have a canonical way to do things. A skill could extend that advantage.

I've been really impressed with Agent Skills as a way to extend the functionality of coding agents. So, I had a thought... A community led and maintained skill for writing Rust. 🧵

I'm very intrigued by OpenCode for one reason:

Ability to switch models quickly without relearning the whole tool.

For those that are using it, has they delivered on this value prop? Or, are you still reworking your workflow when swapping models?

Rust is exploding in the defense space. Is that just because of expanding defense budgets? What other factors are at play here?

Are you guys writing specs for your agents to code from? How are you doing it?

- I assume it's markdown
- Is it multiple files? If so, what is each file for?
- Is there a standard name you always give the file? Or a naming convention?
- Where do the files live?

If you are primarily editing files with a CLI-based agent (Claude Code, Codex, etc.), how are you reviewing the files? In an editor or just right in the terminal with vim or something else lightweight?

Why do people like Zig over Rust?

Is it more of a reaction to a certain culture that exists around Rust than to the technology itself?

Most commentary about the usefulness of coding agents seems to center around web, mobile, etc...

Are the agents similarly effective in real world domains? (embedded, robotics, aerospace, etc.) If not, why not?

Please repost for reach and @ mention those who might have insight!

Is this something you're doing in reaction to AI?

So, let's wade through the uncertainty together! We hope you'll stay for this, but if this isn't what you signed up for, no hard feelings : )

- Drew

Above all, this change in focus comes from an understanding that some in our community are incredibly anxious in this moment. If this is you, know that I feel a ton of empathy for you. But, we all have to keep stumbling forward with whatever information we have.

So, we will continue to post about Rust, and our focus will continue to be on you- this amazing group of Rustaceans that have rallied around filtra. But, we will also focus our attention on asking questions about your (and our) future in the age of AI.

What is clear is that the ground is moving beneath our feet. Anything we say about Rust in particular is less helpful to our community than what light we might be able to shed on the path forward by asking good questions about the future.

To be clear, we don't know whether AI will increase or decrease demand for software engineers.

We don't know whether we should all be getting even better at writing code or becoming product generalists.

We, like you, have virtually no answers.

We think it is very clear that AI is shifting the landscape for our community in a way that eclipses any conversations about Rust.

You might want to unfollow us...

Our content has always been very Rust focused. We love Rust. Beyond the language, we love the Rust community. And, our highest purpose has always been to help those in the community find ways to support their families through rewarding work. 🧵

AI Code Review Is A New, Discrete Skill

We have to learn to discern when we have to understand a snippet of AI generated code deeply and when we don't.

- Bit of UI code that behaves how it should? -> Skim
- Password salt and hash-> CHECK IT

Agree?

a man in a suit and tie is making a sad face in front of a window . ALT: a man in a suit and tie is making a sad face in front of a window .

Elon said Rust is pretty great. Rust people on X:

Been wondering this myself. I suppose one thing that might come into play is the available dataset (either training or to bring into context) it can draw from to inform its implementation.

Oh, also, all signs indicate that xAI is building a model that outputs executables directly. So, check mate!