General Bellard: Years ago, you served us in the International Obfuscated C Code Contest. Now we beg you to help us in our struggle against the Rust Empire. I regret that I am unable to present my request to you in person, but my social media accounts and email have fallen under attack and I'm afraid my mission to bring you to Alderaan has failed. I've placed information vital to the survival of the rebellion into the links below this Hacker News post. My father will know how to retrieve them. You must see these links and half-assed ideas safely delivered to him on Alderaan. This is our most desperate hour. Help me, Obi-Fabrice Bellard. You're my only hope.
Memory safety is boring. Takes all the fun out of writing software. These fucking crab-people take all the joy out of everything. It’s like they don’t even remember the absolute pure surprise of the first time they saw their very first unexpected crash.
They list three problems there. In the first one, they seem to have no idea how allocations work (and haven't even heard of iterators for streaming). In the second one, they're raising a complex topic, okay. As for the third problem, they could solve it with macros. This is a more advanced level of language usage, but they also position themselves as experienced developers.
/uj "Where is the jerk?" That's a seasoned circlejerk response and it's warming me up. Denying there is a jerk around, insisting, demanding to be shown a jerk when the act itself is an evolved part of that jerk, like a jester in court pretending to want to be let in on the jerst.
It's like participating in a Rust discord to later reveal you've never had the understanding to write Rust before, and that you really were only in it for the funny phrases. It asks the question, do Rust developers actually understand Rust. Consequently, have they written a single line of real Rust? Yes they have. Unlike in the first example of the jester, where there is playfulness with the audience's assurance of being entertained, the jest being slung here, by sharing a post just because its form is superficially funny, beckons comments (not yours) that reveal that poster is one to get entertained (for real) by the surface of a post rather mundane and reasonable.
Things I hate: committees, conferences, working with other people, forming a theory of mind.
Things I love: lone geniuses, whig history, dictators that are nice, superheroes, unconfigurable code formatters.
Hey there everybody, this is Bjarne, from Profiles.
Did you know? My favorite things are: Zero-cost abstractions. Multiple inheritance. Implicit casts. The latest Claude Sonnet release. Aaaaand
auto.See you in C++26 everybody!
socialjerk. where is drummer?
Doing buffer overflows to own the libs
General Bellard: Years ago, you served us in the International Obfuscated C Code Contest. Now we beg you to help us in our struggle against the Rust Empire. I regret that I am unable to present my request to you in person, but my social media accounts and email have fallen under attack and I'm afraid my mission to bring you to Alderaan has failed. I've placed information vital to the survival of the rebellion into the links below this Hacker News post. My father will know how to retrieve them. You must see these links and half-assed ideas safely delivered to him on Alderaan. This is our most desperate hour. Help me, Obi-Fabrice Bellard. You're my only hope.
THANK YOU FOR YOUR ATTENTION TO THIS MATTER
Memory safety is boring. Takes all the fun out of writing software. These fucking crab-people take all the joy out of everything. It’s like they don’t even remember the absolute pure surprise of the first time they saw their very first unexpected crash.
The article linked there also looks pretty decent.
https://databento.com/blog/why-we-didnt-rewrite-our-feed-handler-in-rust
They list three problems there. In the first one, they seem to have no idea how allocations work (and haven't even heard of iterators for streaming). In the second one, they're raising a complex topic, okay. As for the third problem, they could solve it with macros. This is a more advanced level of language usage, but they also position themselves as experienced developers.
/uj
re: reusing buffers
There was a blog from the wild dev a while ago that had a neat trick for this. Search "buffer reuse" in https://davidlattimore.github.io/posts/2025/09/02/rustforge-wild-performance-tricks.html
/uj
This is very useful, thank you.
Personally, I would like the compiler to be able to optimize this. It seems that the number of allocations and their allocation type can be inferred.
Where is the jerk?
/uj "Where is the jerk?" That's a seasoned circlejerk response and it's warming me up. Denying there is a jerk around, insisting, demanding to be shown a jerk when the act itself is an evolved part of that jerk, like a jester in court pretending to want to be let in on the jerst.
It's like participating in a Rust discord to later reveal you've never had the understanding to write Rust before, and that you really were only in it for the funny phrases. It asks the question, do Rust developers actually understand Rust. Consequently, have they written a single line of real Rust? Yes they have. Unlike in the first example of the jester, where there is playfulness with the audience's assurance of being entertained, the jest being slung here, by sharing a post just because its form is superficially funny, beckons comments (not yours) that reveal that poster is one to get entertained (for real) by the surface of a post rather mundane and reasonable.
>"/uj"
>proceeds to j
"Oh I'm not masturbating" he says as he looks me in the eyes, grinning, while visibly stroking his cock.
Power move.
Real jerkers never stop jerking
[deleted]
They always are
In the mirror