The game goes like this: start discussing something: say, including rust in OpenBSD.
- Assume it (here, using rust in oBSD) is a great idea.
- For each objection, explain why it is trivial. Your tools are your own reasoning and knowledge of programming, the ability to ignore, minimize or belittle any and all reasons why things are the way they are, assuming away any legacy issues, and remembering that all needs and use-cases in the world exactly match yours.
- When you get bored, just walk away. It isn't your problem, after all, and you were just trying to help. High-fiving your cohort optional.
It ends up simultaneously coming off as arrogant and clueless. Last time I had a small problem and the time to try something new, I started it in rust. After getting a series of jackass responses to a simple question[1], I wrote it in C, because I just don't care enough to put up with twits fluffing their own ego at the expense of newbies.
This problem is hardly unique to rust - unfortunately it happens everywhere nerds gather. But rust has a really bad case of it.
[1] Found the answer a few days later when I thought of a better search term.