the language restriction of rust
Rust has no restriction. The restriction is in his brain high on AI.
make sure to star the github repo so that I can create more projects like these.
That's not how any of this works, he's crazy.
this post was submitted on 06 Jul 2026
268 points (97.2% liked)
Programmer Humor
32560 readers
1176 users here now
Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.
Rules
- Keep content in english
- No advertisements
- Posts must be related to programming or programmer topics
founded 3 years ago
MODERATORS
The language restriction of not knowing the language.
That's not how any of this works, he's crazy.
MF thinks GitHub has “like and subscribe”.
load more comments
(2 replies)
don't you guys pay your rent and buy food with github stars?
As someone who does a lot of freelance and occasionally gets “do it for the exposure” types of gig offers, my go-to response is usually “people die from exposure when they can’t pay their rent.”
Also, you came to me to offer me the gig. I didn’t do any extra work to get you in my inbox. You found my contact info and reached out to me, so I clearly don’t need more exposure.
All this LLM shit just gave crackpots a new tool to annoy the hell out of the rest of us.
I hadn't noticed, I laughed out loud so long, thank you
The language restriction is memory safety by default 🙄
Those are such weird responses, is that user an agent?
Instead of "yes I vibecoded X because of Y" we get the classic respond like you're trying to hit the word limit on your essay.
Sloppers spend so much time talking with their shitbots that they tend to use similar vocabularies and prose. Some of them do have AI write up their responses, too. Some of them even integrate Grok directly into their keyboard.
I hate that I've conditioned my own vocab and tone on the same kind of formal writing that these models have been trained on. I've used en-dashes long before they became a hallmark of botspeak. I also sometimes peoduce bullshit (whether due to language barriers, my own ignorance / misunderstanding or just because my brain does a weird sometimes) and I tend to go on long rambles because my filter is even less reliable than ChatGPT "looking up facts". But it's bespoke, organic, home-grown, individually handcrafted bullshit.
Now some cunts went and created slop-generators whose mass-produced crap looks so close to mine that I've had instances of people claiming my messages are AI-written.
AI isn't taking my job, it's taking my diversion.
What? Like their computer keyboard autocompletes with Grok? Or something else?
I also like how they claim it's completely different to KRunner and then, save for OCR and whatever "circle to search" is, these are all features in KRunner.
Nah, I'm pretty sure every LLM out there knows what Rust has a borrow checker.
load more comments
(1 replies)
I know nothing about rust but I assume borrow checker is some integral part of it that this guy somehow has never heard of?
Yes. Someone that knows just a little more of rust than you do would know what the borrow checker is.
It's the core feature of rust.
Like talking about java and not knowing what "inheritance" is.
EDIT: just so you understand how vibecoded that project is.
The dude says he vibecoded "some of it" because some rust features make it a hard language for him. The one feature he's talking about is the borrow checker.
It's like saying "man, sure is hot today". Someone says "yeah, this summer sure is hot" and the dude replied "yeah, summerians lived in a hot place too".
load more comments
(7 replies)
Very integral. When someone says they're "struggling with Rust", it's thanks to the borrow checker.
Rust's whole shtick is the way it manages memory, which is the rules enforced by the borrow checker.
Basically:
When you want to store values in variables in any programming language, the memory should be allocated when you need it and freed as soon as you don't anymore.
Traditionally there are two ways this is done:
-
You manage it completely yourself, which is "unsafe" as you can forget to free memory you no longer need. This is called leaking memory. Or "reference" the location of something you freed previously, thereby attempting to read data you may not have permission to read (the OS will usually prevent that and kill the program), or reading and using a value you didn't expect, causing undefined behavior and fun to deal with bugs.
-
The language, sometimes using a process which runs alongside your main program, manages memory. Which adds lots of overhead.
Rust has it's own way of doing this: It adds some rules on how you can pass around references and ownership and these rules are affected by whether you can or can't edit the referenced data. All just so the compiler knows the lifetime of the vars that hold that data and when it can free it (before the program is even compiled, so no overhead when the program is running). Not following the strict rules prevents your program from being compiled into an executable.
The compiler gives very helpful info, tips, and pointers™ though, Rust is also know for this.
Thanks for the explanation!
load more comments
(1 replies)
Some would call it the single biggest source of gotcha moments learning the language
load more comments
(1 replies)
load more comments
(1 replies)
Borrow checker? I 'ardly know 'er!
"It's not entirely vibecoded but..." Mmmmhmm. Wish people could just be transparent with themselves and their audiences.
Maybe they edited README.md by hand.
"The chili isn't entirely feces..."
This is the new normal, it seems. My developer colleagues are bragging about how long it has been since they wrote a line of code.
Same.
They always say that so proudly too. "It was all the AI bros!"
me staring at the mountain of shit they just plopped in front of me
Yes, I can tell.
Devs on my team are straight up saying in the sprint retros that the code is slop and needs to be modified after AI makes the suggestion. Our repo is being flooded with garbage that works out of the gate but costs so much extra to troubleshoot when it fails.
load more comments
(1 replies)
My favorite is seeking feedback on reviews on stuff we own and people not responding and being like “I’m sorry I had Claude create 500+ PRs I can’t possibly respond to everything”
You don’t think there’s a problem with that!?!?
Sometimes I lament how long it has been since I wrote a single line of code, because I had to do reviews, testing, management, etc.
I guess some of us like the aspect of coding (as in writing code), while others only like the results (be it the product or the pay)
Yes, I have always enjoyed trying to create elegant architecture and code, more than I get satisfaction from the end result. I've always found it frustrating how many colleagues were prepared to throw together any old junk as long as the right thing came out in the end. On the positive side, maybe the AI does raise the quality of what some of them contribute.
load more comments
(1 replies)
Uses rust because it's memory safe but it is vibe coded and the developer doesn't know what a borrow checker is.
Just use a high level language at this point
load more comments
(7 replies)
Behold, the future of programming.
I really need to keep my (actual) programming skills up to date, because they might be worth a ton of money in some years when everyone will need to unfuck their vibe coded bs.
TBH I only occasionally do some C# and C++ for about 20 years in my spare time, but even if I were hypothetically qualified to fix the world i'm kind of just planning to sit back and watch all of the sloppers go bankrupt for ruining their companies.
load more comments
(5 replies)
"Borrow checker?"
"Thanks bro but don't need your checker got my own"
I don't code in rust, so I had no clue what a borrow checker was before seeing this and looking it up on the side.
Neither did the "developer"
load more comments
(1 replies)
checker?! i hardly know her!
I wouldn't say it was borrowed
Reminds me of a disclaimer in a public domain software package: "No warranty express or implied. If it breaks, you get to keep both pieces."
if rust is too hard, cant you just use another language for your program?
Yes, but then you can’t put in your readme that your blazingly fast new app is written in rust.
No he didn't even open the book to learn it. I'm sure borrow checker is in the beginning.
load more comments
(1 replies)
'Language restriction'. More like ability and/or willingness to learn restriction.
And of course a vibe coder can't write proper sentences with punctuation. If this is what their AI coding chatbot sees, I almost pity it.
We need a programmer_tragedy community for this stuff instead. 💀🤡
You know, this shit makes me wanna learn Rust, it has been long since I really programmed anything.
(Lack of any idea to program more than anything tbh)
I recommend you and everyone start here: https://doc.rust-lang.org/book/
(there's even an interactive version with quizzes, etc)
load more comments
(7 replies)
This is funny, and I do think it's fair to take little jabs at vibe coders, but just be careful. When I was learning to play a game in the past I asked a question. People thought the answer was obvious because the rules were on the thing I was asking about, but I was so new to the game I didn't even know what those words meant. If this was any other context, I'd be hesitant to give someone flak for not knowing a technical term like that. (The context being that somebody vibe coded something.)
On the contrary, the borrow checker is basically the first thing you learn about when writing in Rust as it's the primary "gimmick" of the language. Anyone writing a non-trivial program should have at least heard the term before, even if they don't fully understand how it works.
load more comments
(3 replies)
view more: next ›