When in doubt, just use C# and ASP.NET Core. It's blazing fast. .NET 11 RC2 is even faster. For me, it's the best overall major web framework - auth, config, logging, perf, modular middleware, DI, cross-plat, etc. But I didn't expect this:

Fastest part of Ethereum network is C#

C# FTW again github.com/devmobasa/ttfx Against Python up to 140x faster! Against Rust from 0.3.3 version that DHH referenced here up to 2.12x Since you don't like Rust, you can just port it to a much prettier language like C#, and no need to sacrifice performance. C# on Linux has been such a bliss. So good, and so fast. For bash-like scripts, tools, CLIs, services, apps.

C#/.NET being pushed hard running infrastructure at Ethereum's scale. Nethermind runs on ~3k nodes and accounts for ~33% of staked nodes - supporting a ~$334B native asset, ~$146B of stablecoins and ~$54B deposited in DeFi apps. Nethermind 2.0 has some amazing performance work in it: up to 2.55x block throughput, p99 block processing from 1.65s to 208ms, eth_call RPC 15-27% faster and Keccak-256 ~30% faster with platform intrinsics.

Microsoft recently ported the GitHub Copilot runtime from TypeScript to Rust in roughly 4 months. The entire port was mostly guided by one single engineer and generated a token cost of around $120k. Here are few of my thoughts through my CTO lens. 1. Why Rust and not C#? With AOT, C# was theoretically a possible choice. Yet they decided to use Rust. I'm quite sure this was technically the right choice. But this puts C# and .NET in a tough spot. On the one hand Microsoft hypes the huge performance improvements and the AOT capabilities. Yet for their own products that have to deliver at high scale they chose something else. 2. Mostly one engineer took care of the entire port that was executed mostly by coding agents. However, it's important to note that the engineer doing this was Stephen Toub, which is an absolute god when it comes to performant code and low level programming. So, it was not a random "X expert." Which leads me to put this into the "don't try this at home" category. 3. The $120k cost seems something out of this world for most small and mid-size companies. When it comes to token costs, I think it's always a matter of financial context. I'm quite sure that this port generates enough ROI to make the token cost negligible. The learning point here is that we always need to adapt our agentic coding workflows to the value we generate with the performed work.

fwiw, don't love that OpenAI "launches" aren't actually launches, and the real world availability date is an unknown amount of time down the line. We should all be able to play with this new model together right now, feels weird that only certain people have access.