←back to thread

Introducing tmux-rs

(richardscollin.github.io)
858 points Jtsummers | 2 comments | | HN request time: 0s | source
Show context
johnisgood[dead post] ◴[] No.44457384[source]
[flagged]
_danielle_ ◴[] No.44457563[source]
I mean what else would you expect when C is ported directly to Rust? Rust programs typically aren't written anything like C programs are.
replies(1): >>44458498 #
1. _danielle_ ◴[] No.44458949[source]
Then why make the original comment? :')
replies(1): >>44463166 #
2. johnisgood ◴[] No.44463166[source]
I was stating facts. It is a c2rust project. I do not care about some image they used. I want to see results. For now, it is definitely a c2rust project.

It is not a good look on the community that comments that quote this get flagged:

> https://github.com/richardscollin/tmux-rs/issues/9

> 120 comments and nobody has mentioned the use-after-free triggered by closing a window. Rust truly is the safest language.

Whatever floats your (or their) boat though.

If you have anything against the quote, engage instead of down-voting, or am I expecting much?

And for what it is worth, let me quote the article:

> For the 6 months or so I’ve been quietly porting tmux from C to Rust. I’ve recently reached a big milestone: the code base is now 100% (unsafe) Rust. 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 (excluding comments and empty lines). You might be asking: why did you rewrite tmux in Rust? And yeah, I don’t really have a good reason. It’s a hobby project. Like gardening, but with more segfaults.

Don't you think this is slightly amusing? :D I cannot tell if this is satire or not, by the way.

6 months!