Imagine thinking the borrow checker is just "worse GC." Please at least learn about a language before you try to spread crappy memes about it.
Programmer Humor
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
What? You list metaprogramming as a plus? And functional programming as a minus?
You should rewrite this meme in rust.
thinks functional programming = bad

Tbh the borrow checker isn't a problem for 75% of cases. If you actually need the performance/memory optimization then yes you will have to deal with it... Otherwise just .clone()
And if you find the borrow checker annoying in async rust, that's mostly a tokio issue. Look into smol-rs as it offers alternatives
If you want real cons...
- Compile times
- easy build time arbitrary code execution
- trait bounds spaghetti
- viral async
- viral lifetime annotations
🫣
Viral async?
I've done quite a bit of async programming and I can't quite figure out what people are complaining about here. Best I can tell, they just don't understand what async functions actually are.
Most of the time, async tutorial makes you learn tokio, not async. If your program can run with only tokio::main, then you learned async. If not, you learnt tokio (except if you are spawning a future that should never stop)
For example, my pet project only uses tokio::main to do async stuff. The only instances of tokio::spawn is make sure some SQLite transactions get polled to completion. I do need to replace them with a proper mechanism now that sqlx supports smol-rs
When people say "async is viral" in Rust, they mean that once you make one function async, that change tends to ripple through the rest of your code. Any function that calls it usually has to become async as well so it can await the result. In turn, the callers of those functions often need to become async too.
This propagation can continue all the way up the call stack until you reach your application's entry point. The main exception is when you introduce an explicit synchronous-to-asynchronous boundary, such as by using block_on, which drives the future to completion without requiring the caller itself to be async.
Yeah but it's not really a problem with rust but how the language pattern is made. It's the same in JavaScript/typescript, and Python IIRC
It is Rust implementing the pattern. So... :P
along with most modern languages… it’s the way we deal with async when you don’t want callback hell. it’s just a complex problem domain
like… what… JITs are complex so that’s a problem for V8 specifically?
And if you find the borrow checker annoying in async rust, that’s mostly a tokio issue. Look into smol-rs as it offers alternatives
This is great until you want to use a library which is tokio exclusive, which is most of them.
Well you just need that crate :3
Huh, that pretty cool actually. I need to play around and see if this works with gtk-rs, channels get fairly annoying if you need to use them a lot.
Keep in mind that it doesn't remove tokio from the stack tho. Don't use this to try to improve compilation time
A forbidden compiler
"Don't look a gift horse in the mouth"
No, you probably should look into that horse's mouth to make sure there are no Greeks hiding in it.
"Beware Greeks bearing gifts"
Again, no. You should be wary of gifts bearing Greeks.
Compile time borrow checker is equal to runtime GC, right...
being annoying online
hmm