I have to push back against your assumption that Rust is a language that limits developers. It absolutely does not. As for the AI bit... I use AI to write code all day. It's great, but it makes the same sort of mistakes humans do. I find Rust is a great language for AI to write (under appropriate supervision).

I have fun programming in Rust. I don't like programming in C. I do like programming in C++. I like building type systems that prevent errors and automate drudgery. Both C++ and Rust let me do that, C does not.

I think the point of your "you will have fun programming in C" is that in both languages (and C++) you spend a fair amount of time thinking about low-level details of what the compiler is generating. That's true, and I like thinking about memory layouts, cache lines, what the optimizer is going to do, etc. But I don't like all of the tedium C forces on me.

On balance, I prefer Rust over every other language I've used.

is why I'm sticking to just toggle switches and blinking lights.

Free speech includes lying.

My overall strategy is very different. I don't think Claude's code is remotely good enough yet, so I don't trust it to go off and do "development" semi-unsupervised. I direct and review everything it writes, and I control the scope and content of every commit. To be a little more precise, Claude's code is generally fine (if a bit over-commented), but Claude rarely produces code structure that is clear, clean and correctly-mapped to the problem domain, to my (very picky) eyes. So I never just turn it loose on a large, multi-commit development task.

Entropy is the default state; order and good outcomes are unnatural and require significant energy and focus to impose.

Are you sure you're not an LLM?

I think this is the result of their trainers trying to reduce hallucination. And hallucination *has* been reduced, so it's probably been largely successful, but it has produced this era of versions that are concerned about honesty, that claims of honesty or apologies for lack or honesty, are pervasive in their output.

My iron rule is that Claude is not allowed to modify git state, not even to stage or unstage, and definitely not to commit. As long as that rule is followed, any mistakes can be cleaned up easily.

And even people who don't drive stick regularly (but know how) quickly stop having to pay attention. I haven't owned a stick shift since the mid 90's, but I often get them when renting cars overseas. It takes a day or two of paying attention, and then it just becomes automatic and effortless.

BTDT when coming home from a trip where I'd been driving a manual for a couple of weeks.

About 3% of registered road vehicles are motorcycles. When you include dirt bikes the number of riders is higher, but it's still very low compared to the number of automobile drivers. I don't think motorcycle riders are likely to shift the overall numbers very much.

Reading comprehension is not your strong suit, I see.

I don't know why your reading comprehension is so bad. I would have totally preferred it if any of them knew how to drive a manual or wanted to learn how. But they didn't. How does that make *me* sexist?

The biggest deterrent: Girlfriends and/or wives. They don't know how to operate one, and they have zero interest in learning how. Now you have all sorts of logistical problems.

The guideline in question is "Gotta kick up to the big guy". If you don't pay your "taxes", you're gonna have a bad day. And, no, I'm not talking about the IRS.