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/

[emilianosandri@mastodon.bsd.cafe]

@datenwolf @cwebber I considered learning Rust because I was looking for a modern systems language with modern tooling and without GC but the complicated syntax, the complex toolchain and a lack of a standard is pushing me towards Zig, this is another strong push in that direction.

[duke_of_germany@mastodon.gamedev.place]

Do you happen to have a link at hand for what you read / heard?
@kirtai @cwebber

[dec_hl@mastodon.social]

@emilianosandri @datenwolf @cwebber I dabbled with zig about a year ago and I really liked it...

[ndevenish@mas.to]

@cwebber why are people convinced that “I rewrote it in my style” is a thing. Editing is hard. Changing the “style” of a large block of text is extremely difficult without literally rewriting it from scratch, at which point you should just… write it yourself.

Ask for a list of bullet points to cover if you really are incapable, though probably you shouldn’t be given the job of writing community announcements…

[sharpcheddargoblin@kolektiva.social]

@cwebber I'm more and more convinced that there needs to be a complete moratorium on programming until this LLM shit dies in a fire or the FOSS community purges every LLM booster. Name, shame, and ostracize.

[elpamplina@masto.es]

@cwebber If they rewrote every sentence, why did they need the LLM in the first place? Lies, lies, lies.

[loathsome_dongeater@toots.matapacos.dog]

@cwebber I went when I read 'Async complexity: the "Three Horsemen" problem'

[zaire@fedi.absturztau.be]

@cwebber idk if they realize but, blog posts are supposed to carry meaning

if you have a slop generator spew something out for you that is a most effective admission you actually have nothing to say

[orman@furry.engineer]

@clarfonthey @cwebber Sounds like a description of software in general - there's only a tiny sliver of people who are positive about LLMs but don't say anything

[sharpcheddargoblin@kolektiva.social]

@SRAZKVT I've bounced off of learning Rust from a technical standpoint a few times now, what's the deal with the community? Maybe I'll have to write it off entirely.

[unlambda@hachyderm.io]

@cwebber Fuck. This just sucks so much.

[lumi@snug.moe]

@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

[mi@awawa.cat]

@lumi @cwebber Maintaining a simplistic build tool to replace cargo and enable packaging rust dependencies differently would be a huge motion to disempower their authority. I beg for everyone to endorse such goals whenever they see someone fiddle around the idea.

[navi@social.vlhl.dev]

@mi @lumi @cwebber

https://mesonbuild.com/Rust.html
https://mesonbuild.com/Wrap-dependency-system-manual.html

:3

it's still a pain to do because the tooling expects the cargo workflow, so e.g., system provided crates won't ever be a simple thing until rustc fixes itself

so this would be more of a band-aid than a final solution

[bytebro@mastodonapp.uk]

@cwebber

Splendidly ironic. Muppets.

[powerfromspace1@mstdn.social]

@cwebber ha ha how apropos for our age

[numodular@c.im]

@cwebber But... I just want to... project my inadequacies onto an artificial medium, so I can feel more organically viable...

Yours,
'Unbridled' Capitalism

[hemera@meow.social]

@cwebber Ah fun, and the moment I get LLM vibes I can't help but have my eyes glaze over and I can't ready anymore...

[sibshops@mastodon.online]

@cwebber
> These aren't beginner problems that go away—they're fundamental friction points that manifest differently as developers grow.

Blah

[mi@awawa.cat]

@navi @lumi @cwebber rustc may be not expected to fix itself, and we may need someone to maintain a patch (i don’t like calling it a soft fork, not sure how we describe such projects nowadays)