I'd say TypeScript is currently the best choice for agents. For one, MCP tooling is really solid, the language itself is easy, fast to develop in, and not esoteric.
Can you give me an example of what the borrow checker prevents you from doing without calling Rust developers delusional?
The hardships are way overstated, in my opinion. One issue I can think of newcomers might have is immutable and mutable references. You can't borrow as mutable something already borrowed. Let's say you have a reference to a Vec element, then you add an item to Vec. The realloc could invalidate that reference, which Rust prevents. Using Cell/RefCell also helps if you don't want to deeply nest &mut.
Rust is definitely hard, but after a while it's fine and you kind of get how even if using another language you still have to think about memory.
I hear this constantly but never see any examples of what they actually mean, or it's coming from misunderstandings of what the language is. I've seen people say how well the async code could be if Rust got a garbage collector. For the borrow checker specifically, I think it's important to understand smart pointers, Cell/RefCells, other primitives, and the fact that you don't have to solve everything with references.
Holding him to account is what taxes do, which are allocated by the government. Should taxes be increased? Should there be a wealth tax? I don't care, but it feels wrong when people expect CEOs or investors to somehow fix the world's problems.
I'm seeing this kind of sentiment a lot on hnews, which is weird because it's owned by YC. This is not how investors or businesses work. Government's job is not Sam's job, his job is OpenAI.
I like using "resource names" defined by Google's AIP (https://google.aip.dev/122). For example, the name "users/1/projects/42" is a nested project resource of a user "users/1". TypeScript type could be "users/${number}".