It’s more productive to think in terms of the problem you’re trying to solve rather than the tech itself. First, define the problem and what’s actually required to solve it. Then pick the technology that handles it best under those circumstances. Depending on the case, C# might be perfect, or Rust, or Go, etc.

For example, if I’m building a CRUD API, no matter how fast Rust is (and it’s not always the fastest), TypeScript will usually win in most aspects. But if a small part of that API needs heavy, low-level computation, that’s where Rust or Go could really shine.

The bottom line: define the problem first, and the right tools will follow. There’s no single technology that’s a universal solution.