> ncurses-rs has been archived and will not be further developed. Release 6.0.1 is the last release.
> Overall, the thinness of this wrapper puts it into an uncomfortable middle ground between C and Rust which is still unsafe and not very Rustic. It'd be better to use either C interop directly or something altogether safer. I made ncurses-rs in 2015, when the Rust landscape was very different.
> If you'd like to make a TUI in safe Rust, consider ratatui, cursive, or similar.
Seems reasonable. Author is saying that if they made a TUI today in Rust they wouldn't use ncurses-rs. No point maintaining a library when it stops scratching your own itch
TBH, I'm not sure I'd even use ncurses for a TUI project in C today. ncurses was made to solve a specific set of problems at a specific point in time; better solutions for many of those problems have since emerged.
> ncurses-rs has been archived and will not be further developed. Release 6.0.1 is the last release.
> Overall, the thinness of this wrapper puts it into an uncomfortable middle ground between C and Rust which is still unsafe and not very Rustic. It'd be better to use either C interop directly or something altogether safer. I made ncurses-rs in 2015, when the Rust landscape was very different.
> If you'd like to make a TUI in safe Rust, consider ratatui, cursive, or similar.
Seems reasonable. Author is saying that if they made a TUI today in Rust they wouldn't use ncurses-rs. No point maintaining a library when it stops scratching your own itch
TBH, I'm not sure I'd even use ncurses for a TUI project in C today. ncurses was made to solve a specific set of problems at a specific point in time; better solutions for many of those problems have since emerged.
What would you use then? I am interested!
At this point nearly every terminal understands ANSI escape sequences so that is probably the simplest solution.