The Rust project puts out an article about how they're listening to their community https://blog.rust-lang.org/2026/03/20/rust-challenges/

Except it turns out that article was drafted by an LLM https://www.reddit.com/r/rust/comments/1rz15t3/what_we_heard_about_rusts_challenges_and_how_we/obiwu24/

They claim nearly every line was rewritten by a human but I'm not sure how you could send a worse signal to your community about how much you aren't listening than having an LLM draft a post saying we're really listening, honest

What we heard about Rust's challenges, and how we can address them | Rust Blog

Empowering everyone to build reliable and efficient software.

@cwebber ugh, as someone who loves the rust programming language, it's been so depressing to see everything around it progressively get worse

there are many reasons why i love rust:
- having a haskell-like type system is super nice
- mutable xor shared is a very good idea
- the borrow checker is great to work and promotes having simple ownership graphs
- have a crate as the basic compilation unit, rather than a rust file, is a very sane trade-off, and i like it more than having per-file compilation units
- the culture around correctness is very nice
- rustfmt creating a very consistent way to use rust
- embracing inclusivity from the start

there is a reason why i have "rust is my favorite dirty haskell" on my profile

but then, there are a lot of things which are very bad:
- being co-opted by corporations very quickly
- embracing github and discord
- no stance against proprietary software
- no stance against centralization
- crates.io is very centralized and does not play well with distribution package managers
- cargo being the one blessed build tool, rather than embracing variety
- rust applications being annoying to package properly in distributions

seeing people who i used to respect a lot, like fasterthanlime[0][1] and niko matsakis[2][3][4] embracing the slop machines has also been very depressing

it really makes me look more in the direction of embracing c and zig, but those have their own issues

there is a lot to like about zig, and the project itself seems to have a moral compass[5]. the compiler has a stance against llms and moved away from github. sadly the zig ecosystem does not seem to share this stance. for example ghostty[6] embraces it

0:
ewie.online/posts/20260214-arborium-is-ai-slopw/
1:
github.com/facet-rs/facet/tree/main/.claude
2:
github.com/nikomatsakis/zulook
3:
github.com/nikomatsakis/retcon/tree/main/.claude
4:
github.com/nikomatsakis/dada/tree/main/.claude
5:
codeberg.org/ziglang/zig#strict-no-llm-no-ai-policy
6:
github.com/ghostty-org/ghostty/blob/main/AI_POLICY.md#ai-is-welcome-here
Arborium is AI slopware and should not be trusted - Evie On-Line

It would be an understatement to say that I am mildly interested in syntax highlighting. While I have yet to write a full-fledged parser myself, my blog

@lumi @cwebber Did not know that ghostty embraced AI. Just uninstalled it and switched back to Kitty which is great. Also looking to replace keepassxc because of that.
@marcusxms @lumi @cwebber Arguably the Ghostty solution is at least kinda honest, Kitty silently goes Copilot commits
@natty @cwebber @lumi oh ffs. What about Alacritty? Or any recommendations?
@natty @marcusxms @cwebber gosh i hope alacritty doesn't become slopware
alacritty/CONTRIBUTING.md at master · alacritty/alacritty

A cross-platform, OpenGL terminal emulator. Contribute to alacritty/alacritty development by creating an account on GitHub.

GitHub
@natty @marcusxms @cwebber missed that, woopsie. dummy lumi ​​