Introducing tmux-rs

> the code base is now 100% (unsafe) Rust

So the primary (or rather: only) reason for using Rust over C (memory safety) is out the window.

> I’d like to share the process of porting the original codebase from ~67,000 lines of C code to ~81,000 lines of Rust

And the codebase got bigger.

So yeah, as the author explains, hobby project, and kudos to that, but nothing that I will install on any box of mine any time soon.

Besides, applications like tmux would much rather be prime candidates for a rewrite in a garbage collected systems language (aka.; Go) than in Rust. tmux spends 99% of its time waiting for the user to hit a key, there is nothing performance critical in such an app that wouldn't be 100% adequately served by Go.

Just appalling. Someone publishes a post about their WIP project reaching an important milestone, and here comes the naysayers whining about the fact it's not finished yet.

Did you even the article? He clearly states his aims to convert it to safe rust. And for the code size, he clearly hasn't needed to optimize it yet and I don't think you necessarily want to code golf codebase like this.

The problem is that the "Introducing..." framing generally implies at least a worthwhile MVP, and OP doesn't have that just yet. If it was titled "A feasibility study towards rewriting tmux in Rust" I doubt anyone would've complained.