Having written terminal code both in compiled and interpreted languages, and on machines about a thousand times slower than a typical modern machine, speed here is also much more down to algorithm choices - especially for rendering - than language.
I find the focus on FPS pretty odd as well, as really high update speeds for a terminal typically only comes into play if dumping huge amount of data to the terminal by accident, in which case typically handling scrolling properly is easily speeded up by skipping lines that need never be visible at all.
I do expect terminals I use to be low latency for normal operations, but that's a very different consideration.
Not objecting to your choice of Rust. Just like some others found it odd to highlight it near the top of your main page.
That said, I'll note that unlike Warp it will actually run on Linux...
Writing a tty which has to support specific shells isn't confidence inducing.
How did you paint yourself into that specific corner exactly?
I'd be more careful about the messaging then, something like "you can use any shell you want, we provide enhanced features for bash/zsh/fish and are looking to expand that in future".
We wrote up a pretty detailed technical design if you're interested in checking out how we built and why we made the decisions we made:
https://blog.warp.dev/how-warp-works/